Skip to contentSkip to conversation

docs: Add overview and SLUB allocator sections to slab documentation

PATCH In review Nick Huang 8 participants 18 messages Apr 18 – Apr 20

Subsystems (4)
lore
Share & tools
lore

Nick Huang

author
#0 lore raw

PATCH 1/1 docs: Add overview and SLUB allocator sections to slab documentation

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)
- Highlight SLUB as the default allocator on modern systems
- Add "SLUB Allocator" subsection with detailed information:
- Explain SLUB's design goals and advantages over legacy SLAB
- Document its focus on simplification and performance
- Note support for both uniprocessor and SMP systems

---
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +26 -0
index 2bcc58ada302..2d1d093afb7b 100644
@@ -4,6 +4,32 @@
 Slab Allocation
 ===============
 
+Overview
+========
+
+The slab allocator is responsible for efficient allocation and reuse of
+small kernel objects. It reduces internal fragmentation and improves
+performance by caching frequently used objects.
+
+The Linux kernel provides multiple slab allocator implementations,
+including SLAB, SLUB, and SLOB. Among these, SLUB is the default
+allocator on most modern systems.
+
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.
+
+The primary goal of SLUB is to simplify slab allocation while improving
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.
+
+
 Functions and structures
 ========================
 
Signature · 1 line
2.43.0
#1 lore raw
Quoted 2 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Umm.

commit 6630e950d532

Author: Vlastimil Babka <[email protected]>
Date:   Tue Feb 28 15:38:07 2023 +0100

mm/slob: remove slob.c

commit 16a1d968358a

Author: Vlastimil Babka <[email protected]>
Date:   Mon Oct 2 20:43:43 2023 +0200

mm/slab: remove mm/slab.c and slab_def.h

Care to revise?

Quoted 52 lines

- Highlight SLUB as the default allocator on modern systems
- Add "SLUB Allocator" subsection with detailed information:
- Explain SLUB's design goals and advantages over legacy SLAB
- Document its focus on simplification and performance
- Note support for both uniprocessor and SMP systems

---
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +26 -0
index 2bcc58ada302..2d1d093afb7b 100644
@@ -4,6 +4,32 @@
 Slab Allocation
 ===============
 
+Overview
+========
+
+The slab allocator is responsible for efficient allocation and reuse of
+small kernel objects. It reduces internal fragmentation and improves
+performance by caching frequently used objects.
+
+The Linux kernel provides multiple slab allocator implementations,
+including SLAB, SLUB, and SLOB. Among these, SLUB is the default
+allocator on most modern systems.
+
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.
+
+The primary goal of SLUB is to simplify slab allocation while improving
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.
+
+
 Functions and structures
 ========================
 
Signature · 1 line
2.43.0
author
#2 lore raw

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 13 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Umm.

commit 6630e950d532

Author: Vlastimil Babka <[email protected]>
Date:   Tue Feb 28 15:38:07 2023 +0100

mm/slob: remove slob.c

Quoted 8 lines

commit 16a1d968358a

Author: Vlastimil Babka <[email protected]>
Date:   Mon Oct 2 20:43:43 2023 +0200

mm/slab: remove mm/slab.c and slab_def.h

Care to revise?

Hi Matthew Wilcox

Thanks for pointing this out. You are absolutely right—I overlooked the fact that SLAB and SLOB have been removed from the kernel. I will remove those sections and ensure the documentation focuses on SLUB for the v2 submission. Thanks for the correction.

Quoted 52 lines
Quoted 52 lines

- Highlight SLUB as the default allocator on modern systems
- Add "SLUB Allocator" subsection with detailed information:
- Explain SLUB's design goals and advantages over legacy SLAB
- Document its focus on simplification and performance
- Note support for both uniprocessor and SMP systems

---
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +26 -1
index 2bcc58ada302..2d1d093afb7b 100644
@@ -4,6 +4,32 @@
 Slab Allocation
 ===============
 
+Overview
+========
+
+The slab allocator is responsible for efficient allocation and reuse of
+small kernel objects. It reduces internal fragmentation and improves
+performance by caching frequently used objects.
+
+The Linux kernel provides multiple slab allocator implementations,
+including SLAB, SLUB, and SLOB. Among these, SLUB is the default
+allocator on most modern systems.
+
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.
+
+The primary goal of SLUB is to simplify slab allocation while improving
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.
+
+
 Functions and structures
 ========================
 
--

2.43.0

Signature · 2 lines
Regards,
Nick Huang
author
#3 lore raw

Nick Huang <[email protected]> 於 2026年4月18日週六 下午1:27寫道:

Quoted 6 lines

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 4 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Hi Matthew Wilcox
I will remove this sentence in the next version:
“Document the three main slab allocator implementations (SLAB, SLUB, SLOB).” I’m not entirely sure I fully understand your point. If I’ve missed anything, please let me know what needs to be changed. Thank you.

Quoted 79 lines
Quoted 8 lines

Umm.

commit 6630e950d532

Author: Vlastimil Babka <[email protected]>
Date:   Tue Feb 28 15:38:07 2023 +0100

mm/slob: remove slob.c

Quoted 8 lines

commit 16a1d968358a

Author: Vlastimil Babka <[email protected]>
Date:   Mon Oct 2 20:43:43 2023 +0200

mm/slab: remove mm/slab.c and slab_def.h

Care to revise?

Hi Matthew Wilcox

Thanks for pointing this out. You are absolutely right—I overlooked the fact that SLAB and SLOB have been removed from the kernel. I will remove those sections and ensure the documentation focuses on SLUB for the v2 submission. Thanks for the correction.

Quoted 48 lines
Quoted 48 lines

- Highlight SLUB as the default allocator on modern systems
- Add "SLUB Allocator" subsection with detailed information:
- Explain SLUB's design goals and advantages over legacy SLAB
- Document its focus on simplification and performance
- Note support for both uniprocessor and SMP systems

---
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +26 -0
index 2bcc58ada302..2d1d093afb7b 100644
@@ -4,6 +4,32 @@
 Slab Allocation
 ===============
 
+Overview
+========
+
+The slab allocator is responsible for efficient allocation and reuse of
+small kernel objects. It reduces internal fragmentation and improves
+performance by caching frequently used objects.
+
+The Linux kernel provides multiple slab allocator implementations,
+including SLAB, SLUB, and SLOB. Among these, SLUB is the default
+allocator on most modern systems.
+
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.
+
+The primary goal of SLUB is to simplify slab allocation while improving
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.
+
+
 Functions and structures
 ========================
 
Quoted 4 lines
Quoted 4 lines

--
2.43.0

--
Regards,
Nick Huang

Signature · 2 lines
Regards,
Nick Huang
#8 lore raw
In reply to Nick Huang

Hi, Nick.

Quoted 10 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)
- Highlight SLUB as the default allocator on modern systems
- Add "SLUB Allocator" subsection with detailed information:
- Explain SLUB's design goals and advantages over legacy SLAB
- Document its focus on simplification and performance
- Note support for both uniprocessor and SMP systems

--0

In case this was assisted by AI or other tools, please disclose that according to the process document:

https://docs.kernel.org/process/generated-content.html
https://docs.kernel.org/process/coding-assistants.html

Mentioning because some people using tools to develop/document the kernel are not aware that they need to disclose the fact. It's better to remind people.

Tools can help only if, you, as a person, understand the design and tradeoff behind it. I don't think it'd be useful to spend time on improving document if this is driven by AI tools or something, not you.

If you're using AI or not, the fact that you're not following recent changes of the slab allocator worries me a little bit, to be honest.

Well-written design documentation is hard to come by without understanding the current design.

If you're still willing to improve the doc, please do more research.

Quoted 8 lines
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +0 -0
index 2bcc58ada302..2d1d093afb7b 100644

Documentation/mm/slab.rst line 10

Quoted 7 lines
Documentation/mm/slab.rst +7 -0
@@ -4,6 +4,32 @@
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator

As Matthew mentioned, SLAB and SLOB were gone.
Also, it isn't really the traditional SLUB we have had anymore.

Documentation/mm/slab.rst line 26

Quoted 2 lines
Documentation/mm/slab.rst +2 -0
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.

Stating "Compared to SLAB, SLUB addresses X, Y, and Z" is worth adding only if with a reason explaining why.

If you think SLUB addresses certain problems of SLAB, please explain what problems are and why they exist, and how SLUB addresses that.

Please make more solid arguments with explanations to support.

Documentation/mm/slab.rst line 28

Quoted 1 line
Documentation/mm/slab.rst +1 -0
+The primary goal of SLUB is to simplify slab allocation while improving

I don't think traditional SLUB was particularily simple compared to SLAB, to be honest. It was probably simple at the beginning, but then more and more complexity has been added later.

Documentation/mm/slab.rst line 30

Quoted 2 lines
Documentation/mm/slab.rst +2 -0
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.

SLAB also supported UP and had features to provide scalability on SMP. Why do you think SLUB particularly improved performance on them?

Quoted 3 lines
Documentation/mm/slab.rst +1 -0
+
 Functions and structures
 ========================
Signature · 2 lines
Cheers,
Harry / Hyeonggon
#9 lore raw
In reply to Nick Huang

NAK to obvious, disrespectful, AI slop garbage.

Go read https://docs.kernel.org/process/generated-content.html - especially the bit about dismissing crap like this.

Quoted 2 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

The fact you're insanely wrong about the current state of slab only makes this worse.

Quoted 1 line

- Highlight SLUB as the default allocator on modern systems

Not default. Only...

Quoted 1 line

- Add "SLUB Allocator" subsection with detailed information:

There's nothing detailed...

Quoted 1 line

- Explain SLUB's design goals and advantages over legacy SLAB

Irrelevant, SLAB doesn't exist.

Quoted 1 line

- Document its focus on simplification and performance

Who cares? This isn't linked in?

Quoted 1 line

- Note support for both uniprocessor and SMP systems

Uniprocessor? Seriously?

Quoted 11 lines
---
 Documentation/mm/slab.rst | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
Documentation/mm/slab.rst +0 -0
index 2bcc58ada302..2d1d093afb7b 100644

Documentation/mm/slab.rst line 12

Quoted 9 lines
Documentation/mm/slab.rst +6 -0
@@ -4,6 +4,32 @@
 Slab Allocation
 ===============
 
+Overview
+========
+
+The slab allocator is responsible for efficient allocation and reuse of
+small kernel objects. It reduces internal fragmentation and improves
+performance by caching frequently used objects.

This sentence doesn't even make any sense.

Documentation/mm/slab.rst line 16

Quoted 4 lines
Documentation/mm/slab.rst +4 -0
+
+The Linux kernel provides multiple slab allocator implementations,
+including SLAB, SLUB, and SLOB. Among these, SLUB is the default
+allocator on most modern systems.

WRONG. WRONG. WRONG.

Documentation/mm/slab.rst line 26

Quoted 10 lines
Documentation/mm/slab.rst +10 -0
+
+SLUB Allocator
+==============
+
+Overview
+--------
+
+SLUB is a slab allocator designed to replace the legacy SLAB allocator
+(mm/slab.c). It addresses the complexity, scalability limitations, and
+memory overhead of the SLAB implementation.

This is useless crap? 'X is designed to replace Y which doesn't exist but let's mention it anyway'. How is this an overview?

Documentation/mm/slab.rst line 30

Quoted 4 lines
Documentation/mm/slab.rst +4 -0
+
+The primary goal of SLUB is to simplify slab allocation while improving
+performance on both uniprocessor (UP) and symmetric multiprocessing (SMP)
+systems.

This is meaningless noise too.

Quoted 8 lines
Documentation/mm/slab.rst +2 -1
+
+
 Functions and structures
 ========================
 
--

2.43.0

You've wasted my time, your time and other people's time. Have a think about that.

Lorenzo

#4 lore raw
In reply to Nick Huang
Quoted 4 lines · Nick Huang

Nick Huang <[email protected]> 於 2026年4月18日週六 下午1:27寫道:

Quoted 3 lines

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 1 line
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Hi Matthew Wilcox
I will remove this sentence in the next version:
“Document the three main slab allocator implementations (SLAB, SLUB, SLOB).” I’m not entirely sure I fully understand your point. If I’ve missed anything, please let me know what needs to be changed. Thank you.

No, please don't send any more revisions of this garbage, thanks.

author
#5 lore raw

Hi Lorenzo Stoakes
Lorenzo Stoakes <[email protected]> 於 2026年4月18日週六 下午5:11寫道:

Quoted 9 lines · Nick Huang
Quoted 7 lines

Nick Huang <[email protected]> 於 2026年4月18日週六 下午1:27寫道:

Quoted 6 lines

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 4 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Quoted 7 lines
Quoted 5 lines

Hi Matthew Wilcox
I will remove this sentence in the next version:
“Document the three main slab allocator implementations (SLAB, SLUB, SLOB).” I’m not entirely sure I fully understand your point. If I’ve missed anything, please let me know what needs to be changed. Thank you.

No, please don't send any more revisions of this garbage, thanks.

thank you for your guidance. I will correct my work and introduce the more recent barn, sheave, and kmalloc_obj.
Do you think this is appropriate?

Signature · 2 lines
Regards,
Nick Huang
#6 lore raw
Quoted 17 lines · Nick Huang

Hi Lorenzo Stoakes
Lorenzo Stoakes <[email protected]> 於 2026年4月18日週六 下午5:11寫道:

Quoted 15 lines · Nick Huang
Quoted 12 lines

Nick Huang <[email protected]> 於 2026年4月18日週六 下午1:27寫道:

Quoted 6 lines

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 4 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Hi Matthew Wilcox
I will remove this sentence in the next version:
“Document the three main slab allocator implementations (SLAB, SLUB, SLOB).” I’m not entirely sure I fully understand your point. If I’ve missed anything, please let me know what needs to be changed. Thank you.

Quoted 5 lines
Quoted 1 line

No, please don't send any more revisions of this garbage, thanks.

thank you for your guidance. I will correct my work and introduce the more recent barn, sheave, and kmalloc_obj.
Do you think this is appropriate?

No, this whole thing is inappropriate from the beginning. We are not going to waste more time on development-by-review for something that started as undisclosed LLM slop.

#7 lore raw
Quoted 20 lines · Vlastimil Babka (SUSE)
Quoted 19 lines · Nick Huang

Hi Lorenzo Stoakes
Lorenzo Stoakes <[email protected]> 於 2026年4月18日週六 下午5:11寫道:

Quoted 16 lines · Nick Huang
Quoted 4 lines

Nick Huang <[email protected]> 於 2026年4月18日週六 下午1:27寫道:

Quoted 3 lines

Matthew Wilcox <[email protected]> 於 2026年4月18日週六 下午1:04寫道:

Quoted 1 line
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

Hi Matthew Wilcox
I will remove this sentence in the next version:
“Document the three main slab allocator implementations (SLAB, SLUB, SLOB).” I’m not entirely sure I fully understand your point. If I’ve missed anything, please let me know what needs to be changed. Thank you.

No, please don't send any more revisions of this garbage, thanks.

Quoted 7 lines
Quoted 3 lines

thank you for your guidance. I will correct my work and introduce the more recent barn, sheave, and kmalloc_obj.
Do you think this is appropriate?

No, this whole thing is inappropriate from the beginning. We are not going to waste more time on development-by-review for something that started as undisclosed LLM slop.

Just to be clear, Nick.

I'm no longer willing to answer all of your questions and request for guidance sent in private as you keep ignoring questions & feedback and still looking for other "interesting" items to contribute.

Let's not waste your and others' time.
I don't think this is going to work out.

Expect NACK on your future slab contributions.

Signature · 2 lines
Cheers,
Harry / Hyeonggon
#10 lore raw
In reply to Lorenzo Stoakes
Quoted 6 lines · Lorenzo Stoakes
Quoted 2 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

The fact you're insanely wrong about the current state of slab only makes this worse.

This is actually a new low. We've always had to contend with people putting up outdated or just wrong information on web pages, and there's little we can do about it. Witness all the outdated information about THP that's based on code that's been deleted for over a decade.

But now we've got AI trained on all this wrong/ out of date information, and, er, "enthusiasts" who are trying to change the correct information in the kernel to match what the deluded AI "thinks" should be true.

Let that sink in.

#11 lore raw
Quoted 13 lines · Matthew Wilcox
Quoted 6 lines · Lorenzo Stoakes
Quoted 2 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

The fact you're insanely wrong about the current state of slab only makes this worse.

This is actually a new low. We've always had to contend with people putting up outdated or just wrong information on web pages, and there's little we can do about it. Witness all the outdated information about THP that's based on code that's been deleted for over a decade.

Quoted 6 lines

But now we've got AI trained on all this wrong/ out of date information, and, er, "enthusiasts" who are trying to change the correct information in the kernel to match what the deluded AI "thinks" should be true.

Let that sink in.

I think we should make it very clear that we don't want doc updates from someone that is not a renowned expert in that area or wants to become an expert in that area (and already discussed working on the docs with maintainers/experts).

Otherwise we'll have this same discussion over and over again.

Documentation/mm/index.rst +0 -0
index 7aa2a88869083..8c5721001c8bb 100644
@@ -7,6 +7,11 @@ of Linux.  If you are looking for advice on simply allocating

memory,
see the :ref:memory_allocation. For controlling and tuning guides, see the :doc:admin guide <../admin-guide/mm/index>.

+A lot of documentation in this guide is still incomplete. If you are not +a renowned expert in the specific area, but you want to contribute bigger +chunks of documentation, talk to the respective MM experts first. LLM +generated slop from non-experts will be rejected without further comments. +
.. toctree::
:maxdepth: 1

LLMs are just the tip of the iceberg. It will all be developmend-by review with inexperienced contributors. And we are only willing to put in the effort to teach contributors if the contributors are not actually worth our time: i.e., LLM kiddies that will actually stick around and help the subsystem in the long run.

The whole doc update stuff is similar to people just grepping for TODOs in the kernel and then using an LLM to produce code they have no idea about.

It's the evolution of typo fixes: review load without any benefit.

Signature · 3 lines
Cheers,

David
#12 lore raw
Quoted 14 lines · David Hildenbrand (Arm)
Quoted 13 lines · Matthew Wilcox
Quoted 6 lines · Lorenzo Stoakes
Quoted 2 lines · Nick Huang

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

The fact you're insanely wrong about the current state of slab only makes this worse.

This is actually a new low. We've always had to contend with people putting up outdated or just wrong information on web pages, and there's little we can do about it. Witness all the outdated information about THP that's based on code that's been deleted for over a decade.

Quoted 5 lines
Quoted 5 lines

But now we've got AI trained on all this wrong/ out of date information, and, er, "enthusiasts" who are trying to change the correct information in the kernel to match what the deluded AI "thinks" should be true.

Let that sink in.

Ugh ye gawds. My attitude is nip this in the bud early.

I'm very harsh in response to these things for a reason - firstly, it's rude, obnoxious + disrespectful, so a negative response is wholly appropriate.

But more importantly, I want to SET A PRECEDENT that if you send this crap you'll get a VERY negative response.

Clueless but good faith or bad faith - it's straight up plagiarism and that's totally unacceptable.

Quoted 33 lines
Quoted 1 line

I think we should make it very clear that we don't want doc updates from someone that is not a renowned expert in that area or wants to become an expert in that area (and already discussed working on the docs with maintainers/experts).

Otherwise we'll have this same discussion over and over again.

Documentation/mm/index.rst +5 -0
index 7aa2a88869083..8c5721001c8bb 100644
@@ -7,6 +7,11 @@ of Linux.  If you are looking for advice on simply allocating
 memory,
  see the :ref:`memory_allocation`.  For controlling and tuning guides,
  see the :doc:`admin guide <../admin-guide/mm/index>`.
 
+A lot of documentation in this guide is still incomplete. If you are not
+a renowned expert in the specific area, but you want to contribute bigger
+chunks of documentation, talk to the respective MM experts first. LLM
+generated slop from non-experts will be rejected without further comments.
+
  .. toctree::
     :maxdepth: 1

LLMs are just the tip of the iceberg. It will all be developmend-by review with inexperienced contributors. And we are only willing to put in the effort to teach contributors if the contributors are not actually worth our time: i.e., LLM kiddies that will actually stick around and help the subsystem in the long run.

Quoted 4 lines

The whole doc update stuff is similar to people just grepping for TODOs in the kernel and then using an LLM to produce code they have no idea about.

It's the evolution of typo fixes: review load without any benefit.

Agree with all of that!

Let's do that, happy to give tags on a patch for the above :)

Quoted 6 lines

--
Cheers,

David

Cheers, Lorenzo

author
#13 lore raw

Lorenzo Stoakes <[email protected]> 於 2026年4月19日週日 下午9:17寫道:

Quoted 76 lines · David Hildenbrand (Arm)
Quoted 14 lines · Matthew Wilcox
Quoted 13 lines · Lorenzo Stoakes
Quoted 6 lines · Nick Huang
Quoted 2 lines

- Add "Overview" section explaining the slab allocator's role and purpose
- Document the three main slab allocator implementations (SLAB, SLUB, SLOB)

The fact you're insanely wrong about the current state of slab only makes this worse.

This is actually a new low. We've always had to contend with people putting up outdated or just wrong information on web pages, and there's little we can do about it. Witness all the outdated information about THP that's based on code that's been deleted for over a decade.

Quoted 5 lines
Quoted 5 lines

But now we've got AI trained on all this wrong/ out of date information, and, er, "enthusiasts" who are trying to change the correct information in the kernel to match what the deluded AI "thinks" should be true.

Let that sink in.

Ugh ye gawds. My attitude is nip this in the bud early.

I'm very harsh in response to these things for a reason - firstly, it's rude, obnoxious + disrespectful, so a negative response is wholly appropriate.

But more importantly, I want to SET A PRECEDENT that if you send this crap you'll get a VERY negative response.

Clueless but good faith or bad faith - it's straight up plagiarism and that's totally unacceptable.

Quoted 33 lines
Quoted 1 line

I think we should make it very clear that we don't want doc updates from someone that is not a renowned expert in that area or wants to become an expert in that area (and already discussed working on the docs with maintainers/experts).

Otherwise we'll have this same discussion over and over again.

Documentation/mm/index.rst +5 -0
index 7aa2a88869083..8c5721001c8bb 100644
@@ -7,6 +7,11 @@ of Linux.  If you are looking for advice on simply allocating
 memory,
  see the :ref:`memory_allocation`.  For controlling and tuning guides,
  see the :doc:`admin guide <../admin-guide/mm/index>`.
 
+A lot of documentation in this guide is still incomplete. If you are not
+a renowned expert in the specific area, but you want to contribute bigger
+chunks of documentation, talk to the respective MM experts first. LLM
+generated slop from non-experts will be rejected without further comments.
+
  .. toctree::
     :maxdepth: 1

LLMs are just the tip of the iceberg. It will all be developmend-by review with inexperienced contributors. And we are only willing to put in the effort to teach contributors if the contributors are not actually worth our time: i.e., LLM kiddies that will actually stick around and help the subsystem in the long run.

Quoted 4 lines

The whole doc update stuff is similar to people just grepping for TODOs in the kernel and then using an LLM to produce code they have no idea about.

It's the evolution of typo fixes: review load without any benefit.

Agree with all of that!

Let's do that, happy to give tags on a patch for the above :)

Quoted 1 line
Quoted 7 lines
Quoted 5 lines

--
Cheers,

David

Cheers, Lorenzo

Hi Lorenzo Stoakes

I am really sorry for causing trouble for everyone. I would like to ask which aspect of mine was disrespectful, so that I can be more careful next time.

If I want to make this kind of change, should I send an [RFC patch] to ask for everyone's opinion?

Sorry, I really am not very clear about the process.

Signature · 2 lines
Regards,
Nick Huang
reviewer
#14 lore raw

Hi Nick,

Quoted 4 lines · Nick Huang

I am really sorry for causing trouble for everyone. I would like to ask which aspect of mine was disrespectful, so that I can be more careful next time.

Maintainers time is valuable and sending LLM generated patch completely without understanding what it is about is disrespect for maintainers wasted time.

Quoted 2 lines

If I want to make this kind of change, should I send an [RFC patch] to ask for everyone's opinion?

If you want to make that kind of change, you should start with researching and understanding yourself what the code is doing, double check the LLM output and verify it and not just take an LLM slop and send it.

Quoted 1 line

Sorry, I really am not very clear about the process.

Start with reading kernel process documentation:
https://docs.kernel.org/process/development-process.html

Quoted 3 lines
Signature · 2 lines
Regards,
Nick Huang
Signature · 2 lines
Sincerely yours,
Mike.
maintainer
#16 lore raw
In reply to Nick Huang
Quoted 6 lines · Nick Huang

I am really sorry for causing trouble for everyone. I would like to ask which aspect of mine was disrespectful, so that I can be more careful next time.

If I want to make this kind of change, should I send an [RFC patch] to ask for everyone's opinion?

If you want to be respectful, start by reading what has been sent to you; the problems with your submission were well explained, more than once.

To reiterate:

- Do not send LLM-generated material without marking it as such as described in our developer documentation.

- Do not attempt to document systems that you do not, yourself, understand; you have no hope of getting it right, and you will only succeed in wasting the time of the people who have to review your changes.

The point of documentation is to be informative, accurate, and useful; simply filling in a bunch of words is not helpful to anybody.

Thanks,

jon

author
#15 lore raw
In reply to Mike Rapoport

Mike Rapoport <[email protected]> 於 2026年4月20日週一 下午2:42寫道:

Quoted 25 lines

Hi Nick,

Quoted 4 lines · Nick Huang

I am really sorry for causing trouble for everyone. I would like to ask which aspect of mine was disrespectful, so that I can be more careful next time.

Maintainers time is valuable and sending LLM generated patch completely without understanding what it is about is disrespect for maintainers wasted time.

Quoted 2 lines

If I want to make this kind of change, should I send an [RFC patch] to ask for everyone's opinion?

If you want to make that kind of change, you should start with researching and understanding yourself what the code is doing, double check the LLM output and verify it and not just take an LLM slop and send it.

Quoted 1 line

Sorry, I really am not very clear about the process.

Start with reading kernel process documentation:
https://docs.kernel.org/process/development-process.html

Quoted 7 lines
Quoted 3 lines

--
Regards,
Nick Huang

--
Sincerely yours,
Mike.

Thank you for your suggestion. I will read the kernel process documentation carefully.

Signature · 2 lines
Regards,
Nick Huang
author
#17 lore raw
In reply to Jonathan Corbet

Jonathan Corbet <[email protected]> 於 2026年4月20日週一 下午2:43寫道:

Quoted 24 lines
Quoted 6 lines · Nick Huang

I am really sorry for causing trouble for everyone. I would like to ask which aspect of mine was disrespectful, so that I can be more careful next time.

If I want to make this kind of change, should I send an [RFC patch] to ask for everyone's opinion?

If you want to be respectful, start by reading what has been sent to you; the problems with your submission were well explained, more than once.

To reiterate:

- Do not send LLM-generated material without marking it as such as described in our developer documentation.

- Do not attempt to document systems that you do not, yourself, understand; you have no hope of getting it right, and you will only succeed in wasting the time of the people who have to review your changes.

Quoted 6 lines

The point of documentation is to be informative, accurate, and useful; simply filling in a bunch of words is not helpful to anybody.

Thanks,

jon

Thank you for your feedback.

Signature · 2 lines
Regards,
Nick Huang