From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: "shakeelb@google.com" <shakeelb@google.com>,
"willy@infradead.org" <willy@infradead.org>,
"tj@kernel.org" <tj@kernel.org>,
"dennis@kernel.org" <dennis@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: lkp <lkp@intel.com>,
"zhengjun.xing@linux.intel.com" <zhengjun.xing@linux.intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Tang, Feng" <feng.tang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"Sang, Oliver" <oliver.sang@intel.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>
Subject: Re: [linus:master] [mm] f1a7941243: unixbench.score -19.2% regression
Date: Mon, 27 Feb 2023 06:35:31 +0000 [thread overview]
Message-ID: <d5d0bcf75cbaa2792a3ad0e7b15a84fd67e54454.camel@intel.com> (raw)
In-Reply-To: <CALvZod7TuaJ7pCc2nJKehwGkcuvsvjdL+4hs6qC3bZsOmGzXzg@mail.gmail.com>
Hi Andrew, Shakeel,
On Tue, 2023-01-31 at 10:26 -0800, Shakeel Butt wrote:
> +per-cpu memory maintainers for FYI.
>
> Thread started at
> https://lore.kernel.org/linux-mm/202301301057.e55dad5b-oliver.sang@intel.com/
>
> On Mon, Jan 30, 2023 at 9:57 PM Shakeel Butt <shakeelb@google.com>
> wrote:
> >
> [...]
> > >
> > > We could cut down the number of calls to pcpu_alloc() by a factor
> > > of 4
> > > by having a pcpu_alloc_bulk() that would allocate all four RSS
> > > counters
> > > at once.
> > >
> > > Just throwing out ideas ...
> >
> > Thanks, I will take a stab at pcpu_alloc_bulk() and will share the
> > result tomorrow.
> >
>
> OK, not a one day effort.
>
> Andrew, which option do you prefer?
>
> 1. Keep the patches as the test workload (fork ping pong) is not a
> representative of real world workload and work on improving
> pcpu_alloc() for 6.4+.
>
> 2. Revert the patches for now, improve pcpu_alloc() and re-introduce
> the patches once we confirm that fork-ping-pong is not regressed
> anymore.
This performance regression still can be reproduced on latest master
branch. So we took option1 here. Right? Thanks.
Regards
Yin, Fengwei
>
> thanks,
> Shakeel
next prev parent reply other threads:[~2023-02-27 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:32 [linus:master] [mm] f1a7941243: unixbench.score -19.2% regression kernel test robot
2023-01-30 4:15 ` Matthew Wilcox
2023-01-31 5:23 ` Shakeel Butt
2023-01-31 5:45 ` Matthew Wilcox
2023-01-31 5:57 ` Shakeel Butt
2023-01-31 18:26 ` Shakeel Butt
2023-02-27 6:35 ` Yin, Fengwei [this message]
2023-02-27 16:50 ` Shakeel Butt
2023-02-28 0:32 ` Yin, Fengwei
2023-01-31 6:11 ` Feng Tang
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=d5d0bcf75cbaa2792a3ad0e7b15a84fd67e54454.camel@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dennis@kernel.org \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=m.szyprowski@samsung.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@linux.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;
as well as URLs for NNTP newsgroup(s).