linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Harry Yoo <harry.yoo@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	linux-mm@kvack.org
Subject: Re: [RFC v1 0/2] slabinfo: sheaves statistics support
Date: Fri, 25 Apr 2025 17:16:07 +0900	[thread overview]
Message-ID: <aAtEx4zhyPTenCk9@harry> (raw)
In-Reply-To: <e622a4b5-a321-4ee5-a7b2-b99063e0ccb6@suse.cz>

On Wed, Apr 23, 2025 at 04:28:59PM +0200, Vlastimil Babka wrote:
> On 4/7/25 06:37, Harry Yoo wrote:
> > On Mon, Apr 07, 2025 at 01:18:08PM +0900, Harry Yoo wrote:
> >> With this series, `slabinfo -r` now prints sheaves statistics (if enabled).
> >> Written on top of slub-percpu-sheaves-v4r0 [1] branch.
> 
> Thanks!
> 
> >> Q1: Vlastimil, do you want to integrate this into the sheaves series or do
> >> you want me to send it as a follow-up series after sheaves land mainline?
> 
> I think it's fine to do patch 2 a follow-up.

Alright.

> As for patch 1 I will instead
> export sheaf_capacity as part of the initial support.

Thanks! 'sheaf_capacity' sounds fine to me.

> >> Q2: 'sheaf_swap' does not fit into the table because SLUB swaps sheaves both
> >> at alloc and free. Probably split the counter?
> 
> I'm considering just dropping it instead as it's not that useful as a
> measure of caching efficiency? Probably sheaf_flush_main also doesn't need
> to be a separate counter as it only happens in corner cases.

No strong opinion from me.
Not adding it will be fine as we can add it later if needed.

> Due to ABI becoming set in stone we should be conservative.

Agreed.

> > Q3: Having 'Add sheaves to the barn' & 'Remove sheaves from the barn' counters
> > might help better understand the behavior? (just like 'Add partial' /
> > 'Remove partial' pair in the normal SLUB path).
> 
> Yeah that could make more sense instead I think,

-- 
Cheers,
Harry / Hyeonggon


      reply	other threads:[~2025-04-25  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  4:18 Harry Yoo
2025-04-07  4:18 ` [RFC v1 1/2] mm/slab: add sheaves_enabled read-only sysfs file Harry Yoo
2025-04-09  2:45   ` David Rientjes
2025-04-10 22:32     ` Harry Yoo
2025-04-23 14:24       ` Vlastimil Babka
2025-04-07  4:18 ` [RFC v1 2/2] tools/mm/slabinfo: add support for sheaves stats Harry Yoo
2025-04-07  4:37 ` [RFC v1 0/2] slabinfo: sheaves statistics support Harry Yoo
2025-04-23 14:28   ` Vlastimil Babka
2025-04-25  8:16     ` Harry Yoo [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=aAtEx4zhyPTenCk9@harry \
    --to=harry.yoo@oracle.com \
    --cc=cl@linux.com \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    /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