From: Shakeel Butt <shakeel.butt@linux.dev>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Yosry Ahmed <yosryahmed@google.com>,
"T.J. Mercier" <tjmercier@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
cgroups@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [memcg] 70a64b7919: will-it-scale.per_process_ops -11.9% regression
Date: Fri, 24 May 2024 11:06:54 -0700 [thread overview]
Message-ID: <uzqh6xvoe6xgef3i6743m7gld5tlqp6h2krcqgjre3nzfcogwz@gsllvs77r57a> (raw)
In-Reply-To: <ZlBFskeX3Wj3UGYJ@xsang-OptiPlex-9020>
On Fri, May 24, 2024 at 03:45:54PM +0800, Oliver Sang wrote:
> hi, Shakeel,
>
[...]
>
> >
> > 1. What is the baseline kernel you are using? Is it linux-next or linus?
> > If linux-next, which one specifically?
>
> base is just 59142d87ab03b, which is in current linux-next/master,
> and is already merged into linus/master now.
>
> linux$ git rev-list linux-next/master | grep 59142d87ab03b
> 59142d87ab03b8ff969074348f65730d465f42ee
>
> linux$ git rev-list linus/master | grep 59142d87ab03b
> 59142d87ab03b8ff969074348f65730d465f42ee
>
>
> the data for it is the first column in the tables we supplied.
>
> I just applied your patch upon a94032b35e5f9, so:
>
> linux$ git log --oneline --graph fd2296741e2686ed6ecd05187e4
> * fd2296741e268 fix for 70a64b7919 from Shakeel <----- your fix patch
> * a94032b35e5f9 memcg: use proper type for mod_memcg_state <--- patch-set tip, I believe
> * acb5fe2f1aff0 memcg: warn for unexpected events and stats
> * 4715c6a753dcc mm: cleanup WORKINGSET_NODES in workingset
> * 0667c7870a186 memcg: cleanup __mod_memcg_lruvec_state
> * ff48c71c26aae memcg: reduce memory for the lruvec and memcg stats
> * aab6103b97f1c mm: memcg: account memory used for memcg vmstats and lruvec stats
> * 70a64b7919cbd memcg: dynamically allocate lruvec_stats <--- we reported this as 'fbc' in original report
> * 59142d87ab03b memcg: reduce memory size of mem_cgroup_events_index <--- base
>
Cool, let's stick to the linus tree. I was actually taking next-20240521
and reverting all the patches in the series to treat as the base. One
request I have would be to make the base the patch previous to the
59142d87ab03b i.e. not 59142d87ab03b.
>
> >
> > 2. What is the cgroup hierarchy where the workload is running? Is it
> > running in the root cgroup?
>
> Our test system uses systemd from the distribution (debian-12). The workload is
> automatically assigned to a specific cgroup by systemd which is in the
> sub-hierarchy of root, so it is not directly running in the root cgroup.
>
> >
> > 3. For the followup experiments when needed, can you please remove the
> > whole series (including 59142d87ab03b8ff) for the base numbers.
>
> I cannot understand this very well, if the patch is to fix the regression
> cause by this series, seems to me the best way is to apply this patch on top
> of the series. anything I misunderstood here?
>
Sorry I just meant to make the 'base' case to compare against the commit
previous to 59142d87ab03b as I said above.
I will re-run my experiments on linus tree and report back.
next prev parent reply other threads:[~2024-05-24 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 5:56 kernel test robot
2024-05-17 23:38 ` Yosry Ahmed
2024-05-18 6:28 ` Shakeel Butt
2024-05-19 9:14 ` Oliver Sang
2024-05-19 17:20 ` Shakeel Butt
2024-05-20 2:43 ` Oliver Sang
2024-05-20 3:49 ` Shakeel Butt
2024-05-21 2:43 ` Oliver Sang
2024-05-22 4:18 ` Shakeel Butt
2024-05-23 7:48 ` Oliver Sang
2024-05-23 16:47 ` Shakeel Butt
2024-05-24 7:45 ` Oliver Sang
2024-05-24 18:06 ` Shakeel Butt [this message]
2024-05-28 6:30 ` Shakeel Butt
2024-05-30 6:17 ` Oliver Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uzqh6xvoe6xgef3i6743m7gld5tlqp6h2krcqgjre3nzfcogwz@gsllvs77r57a \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=roman.gushchin@linux.dev \
--cc=tjmercier@google.com \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox