linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Christoph Lameter <cl@gentwo.org>,
	David Rientjes <rientjes@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Harry Yoo <harry.yoo@oracle.com>
Subject: Re: [PATCH] MAINTAINERS: add missing files to slab section
Date: Wed, 23 Jul 2025 11:16:07 +0100	[thread overview]
Message-ID: <0008a3ea-ae9b-4425-b3e8-c6eedf9bb7f3@lucifer.local> (raw)
In-Reply-To: <a3f60194-3498-4dce-b0f0-e16e706f66ee@suse.cz>

On Wed, Jul 23, 2025 at 12:07:39PM +0200, Vlastimil Babka wrote:
> On 7/22/25 19:59, Lorenzo Stoakes wrote:
> > The failslab implementation implements fault injection for slab allocations
> > so seems best suited to the slab section.
> >
> > The mempool implementation uses slab in the backend, so that seems best
> > suited here also.
>
> It has other backends too but perhaps slab is the most complex and David was
> involved so seems acceptable.

Thanks

>
> >
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > ---
> > NOTE:
> >
> > To try to reduce conflicts with the latest batch of MAINTAINERS changes, I
> > think this is best merged through the slab tree.
> >
> >  MAINTAINERS | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index e55accbef..2d5c844ab 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -15738,7 +15738,6 @@ F:	include/linux/memfd.h
> >  F:	include/linux/memory_hotplug.h
> >  F:	include/linux/memory-tiers.h
> >  F:	include/linux/mempolicy.h
> > -F:	include/linux/mempool.h
> >  F:	include/linux/memremap.h
> >  F:	include/linux/mmzone.h
> >  F:	include/linux/mmu_notifier.h
>
> I'll leave out this hunk as your other patch moves the header entry from MM
> to MM-MISC (maybe it could be removing it there while at it?).

OK let's just fix this up later potentially, I don't want to create more
confusion at this stage :P

I guess with this being potentially used elsewhere, this actually makes sense.

>
> > @@ -22831,7 +22830,10 @@ S:	Maintained
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git
> >  F:	Documentation/admin-guide/mm/slab.rst
> >  F:	Documentation/mm/slab.rst
> > +F:	include/linux/mempool.h
> >  F:	include/linux/slab.h
> > +F:	mm/failslab.c
> > +F:	mm/mempool.c
> >  F:	mm/slab.h
> >  F:	mm/slab_common.c
> >  F:	mm/slub.c
> > --
> > 2.50.1
>


      reply	other threads:[~2025-07-23 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 17:59 Lorenzo Stoakes
2025-07-23 10:07 ` Vlastimil Babka
2025-07-23 10:16   ` Lorenzo Stoakes [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=0008a3ea-ae9b-4425-b3e8-c6eedf9bb7f3@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=cl@gentwo.org \
    --cc=harry.yoo@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --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