linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosryahmed@google.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Shakeel Butt <shakeel.butt@linux.dev>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 "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, 17 May 2024 16:38:28 -0700	[thread overview]
Message-ID: <CAJD7tkbsvRpYTkrjZ8k2ArQSaU+YkF=6rqtVHdjd1ovErvUE6w@mail.gmail.com> (raw)
In-Reply-To: <202405171353.b56b845-oliver.sang@intel.com>

On Thu, May 16, 2024 at 10:56 PM kernel test robot
<oliver.sang@intel.com> wrote:
>
>
>
> Hello,
>
> kernel test robot noticed a -11.9% regression of will-it-scale.per_process_ops on:
>
>
> commit: 70a64b7919cbd6c12306051ff2825839a9d65605 ("memcg: dynamically allocate lruvec_stats")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

I think we may want to go back to the approach of reordering the
indices to separate memcg and non-memcg stats. If we really want to
conserve the order in which the stats are exported to userspace, we
can use a translation table on the read path instead of the update
path.


  reply	other threads:[~2024-05-17 23:39 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 [this message]
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
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='CAJD7tkbsvRpYTkrjZ8k2ArQSaU+YkF=6rqtVHdjd1ovErvUE6w@mail.gmail.com' \
    --to=yosryahmed@google.com \
    --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=shakeel.butt@linux.dev \
    --cc=tjmercier@google.com \
    --cc=ying.huang@intel.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