All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	Seongjun Hong <hsj0512@snu.ac.kr>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Christoph Lameter <cl@gentwo.org>
Subject: Re: [PATCH] docs: ABI: sysfs-kernel-slab: mark cpu_partial attributes deprecated
Date: Fri, 3 Jul 2026 14:12:59 +0900	[thread overview]
Message-ID: <77a03a9a-8461-40c3-a383-d9dc62efb801@kernel.org> (raw)
In-Reply-To: <f047ceae-4836-40c9-bb7c-a6074bbf1a1f@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 2322 bytes --]



On 7/2/26 5:28 PM, Vlastimil Babka (SUSE) wrote:
> On 7/2/26 07:18, Harry Yoo wrote:
>>
>>
>> On 7/1/26 11:17 PM, Seongjun Hong wrote:
>>> The per-cpu slab and per-cpu partial slab mechanisms were removed when
>>> SLUB was converted to per-cpu sheaves in Linux 7.0. The cpu_slabs,
>>
>> small nit: sheaves were introduced in v6.18,
>> but the cpu (partial) slabs layer were removed later in v7.0.
> 
> Fixed up when applying by saying "fully converted" :)

Looks good, thanks!

>>> slabs_cpu_partial and cpu_partial sysfs attributes were kept as stubs
>>> that always return 0 for backwards compatibility, but their
>>> documentation still described them as if they were functional.
>>
>> Right, for backward compatibility, because, unlike files that
>> might not exist w/o SLUB_STATS, userspace tools might assume that
>> they always exist.
>>
>>> Update the three descriptions to state that the attributes are
>>> deprecated and always read 0, and note that they are retained only for
>>> compatibility. While here, fix a "partialli" typo in the
>>> slabs_cpu_partial description.
>>>
>>> Signed-off-by: Seongjun Hong <hsj0512@snu.ac.kr>
>>> ---
>>
>> Overall looks good to me, so:
>> Acked-by: Harry Yoo (Oracle) <harry@kernel.org>
> 
> Added to slab/for-next, thanks!

Thanks!

>> By the way.
>>
>> There's still some gap between the documentation
>> and the implementation :)
>>
>> We've dropped a bunch of files that exist only on
>> SLUB_STATS and new files introduced with by
>> sheaves were not documented.
> 
> While we are touching these files, the question is what contact to use
> there. Some have Christoph, some Pekka, some both.
> Seems inflexible to me and should ideally point to the slab MAINTAINERS
> entry.

Agreed.

> But not sure if it's possible. Documentation/ABI/README says:
> 
> Contact:        Primary contact for this interface (may be a mailing list)

Looking at other mm-related sysfs files:

Contact:	Linux memory management mailing list <linux-mm@kvack.org>

> Maybe we can propose that it can also say
> 
> See the SLAB ALLOCATOR subsystem in MAINTAINERS.

Replacing the contact with linux-mm mailing list and mentioning
SLAB ALLOCATOR subsystem in MAINTAINERS sounds good to me.

-- 
Cheers,
Harry / Hyeonggon

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-07-03  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 14:17 [PATCH] docs: ABI: sysfs-kernel-slab: mark cpu_partial attributes deprecated Seongjun Hong
2026-07-02  5:18 ` Harry Yoo
2026-07-02  8:28   ` Vlastimil Babka (SUSE)
2026-07-03  5:12     ` 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=77a03a9a-8461-40c3-a383-d9dc62efb801@kernel.org \
    --to=harry@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=hsj0512@snu.ac.kr \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.