linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: "Song, Xiongwei" <Xiongwei.Song@windriver.com>,
	"rientjes@google.com" <rientjes@google.com>,
	"cl@linux.com" <cl@linux.com>,
	"penberg@kernel.org" <penberg@kernel.org>,
	"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"roman.gushchin@linux.dev" <roman.gushchin@linux.dev>,
	"42.hyeyoo@gmail.com" <42.hyeyoo@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"chengming.zhou@linux.dev" <chengming.zhou@linux.dev>
Subject: Re: [PATCH 3/4] mm/slub: simplify get_partial_node()
Date: Wed, 3 Apr 2024 09:25:33 +0200	[thread overview]
Message-ID: <2cab01ce-7c5f-46d6-b8a4-c2a24c3f9a32@suse.cz> (raw)
In-Reply-To: <PH0PR11MB5192C3A3806D89D0CACC2CEEEC3D2@PH0PR11MB5192.namprd11.prod.outlook.com>

On 4/3/24 2:37 AM, Song, Xiongwei wrote:
>> 
>> 
>> It could be tempting to use >= instead of > to achieve the same effect but
>> that would have unintended performance effects that would best be evaluated
>> separately.
> 
> I can run a test to measure Amean changes. But in terms of x86 assembly, there 
> should not be extra  instructions with ">=".
> 
> Did a simple test, for ">=" it uses "jle" instruction, while "jl" instruction is used for ">".
> No more instructions involved. So there should not be performance effects on x86.

Right, I didn't mean the code of the test, but how the difference of the
comparison affects how many cpu partial slabs would be put on the cpu
partial list here.

> Thanks,
> Xiongwei
> 
>> 
>> >
>> > +             put_cpu_partial(s, slab, 0);
>> > +             stat(s, CPU_PARTIAL_NODE);
>> > +             partial_slabs++;
>> > +
>> > +             if (partial_slabs > slub_get_cpu_partial(s) / 2)
>> > +                     break;
>> >       }
>> >       spin_unlock_irqrestore(&n->list_lock, flags);
>> >       return partial;
> 



  reply	other threads:[~2024-04-03  7:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31  2:19 [PATCH 0/4] SLUB: improve filling cpu partial a bit in get_partial_node() xiongwei.song
2024-03-31  2:19 ` [PATCH 1/4] mm/slub: remove the check of !kmem_cache_has_cpu_partial() xiongwei.song
2024-04-02  9:45   ` Vlastimil Babka
2024-04-03  0:10     ` Song, Xiongwei
2024-03-31  2:19 ` [PATCH 2/4] mm/slub: add slub_get_cpu_partial() helper xiongwei.song
2024-03-31  2:19 ` [PATCH 3/4] mm/slub: simplify get_partial_node() xiongwei.song
2024-04-02  9:41   ` Vlastimil Babka
2024-04-03  0:37     ` Song, Xiongwei
2024-04-03  7:25       ` Vlastimil Babka [this message]
2024-04-03 11:15         ` Song, Xiongwei
2024-03-31  2:19 ` [PATCH 4/4] mm/slub: don't read slab->cpu_partial_slabs directly xiongwei.song
2024-04-02  9:42   ` Vlastimil Babka
2024-04-03  0:11     ` Song, Xiongwei

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=2cab01ce-7c5f-46d6-b8a4-c2a24c3f9a32@suse.cz \
    --to=vbabka@suse.cz \
    --cc=42.hyeyoo@gmail.com \
    --cc=Xiongwei.Song@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=chengming.zhou@linux.dev \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    /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