linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Brown <broonie@kernel.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Bert Karwatzki <spasswolf@web.de>, Jeff Xu <jeffxu@chromium.org>,
	Jiri Olsa <olsajiri@gmail.com>, Kees Cook <kees@kernel.org>,
	Lorenzo Stoakes <lstoakes@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Paul Moore <paul@paul-moore.com>,
	Sidhartha Kumar <sidhartha.kumar@oracle.com>,
	"Suren Baghdasaryan" <surenb@google.com>, <linux-mm@kvack.org>,
	<ying.huang@intel.com>, <feng.tang@intel.com>,
	<fengwei.yin@intel.com>, <oliver.sang@intel.com>
Subject: Re: [linus:master] [mm]  cacded5e42:  aim9.brk_test.ops_per_sec -5.0% regression
Date: Fri, 18 Oct 2024 08:34:28 +0800	[thread overview]
Message-ID: <ZxGtFCzk5kwycFV3@xsang-OptiPlex-9020> (raw)
In-Reply-To: <ac1e101c-f3ed-4e9a-9ef4-37788fce4680@lucifer.local>

hi, Lorenzo,

On Thu, Oct 17, 2024 at 09:54:13AM +0100, Lorenzo Stoakes wrote:
> On Thu, Oct 17, 2024 at 10:58:38AM +0800, Oliver Sang wrote:

[...]

> 
> Thanks for this. As far as I'm concerned this puts us into noise territory,
> so we'll go with this as the solution!
> 
> A side-note, the brk2 test from the will-it-scale suite, written explicitly
> to be more real-world representative, sees an actual performance
> _improvement_ here (though small).
> 
> So overall I'm comfortable with this, we can revisit if anybody raises any
> objection! The benefit in de-duplicating code is very significant.

thanks a lot for all these informations!

> 
> Thanks for all your help, hugely appreciated!

you are welcome :) just our great pleasure!

> 
> Cheers, Lorenzo
> 
> [snip]


      reply	other threads:[~2024-10-18  0:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  2:21 kernel test robot
2024-09-30  8:21 ` Lorenzo Stoakes
2024-10-08  8:31   ` Oliver Sang
2024-10-08  8:44     ` Lorenzo Stoakes
2024-10-09  6:44       ` Oliver Sang
2024-10-09  9:52         ` Lorenzo Stoakes
2024-10-09 21:24         ` Lorenzo Stoakes
2024-10-11  2:46           ` Oliver Sang
2024-10-11  7:26             ` Lorenzo Stoakes
2024-10-15 19:56               ` Lorenzo Stoakes
2024-10-17  2:58                 ` Oliver Sang
2024-10-17  8:54                   ` Lorenzo Stoakes
2024-10-18  0:34                     ` Oliver Sang [this message]

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=ZxGtFCzk5kwycFV3@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=jeffxu@chromium.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lstoakes@gmail.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=olsajiri@gmail.com \
    --cc=paul@paul-moore.com \
    --cc=paulmck@kernel.org \
    --cc=sidhartha.kumar@oracle.com \
    --cc=spasswolf@web.de \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --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