linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Nick Huang <sef1548@gmail.com>, Lorenzo Stoakes <ljs@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
	Harry Yoo <harry@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Hao Li <hao.li@linux.dev>,
	Christoph Lameter <cl@gentwo.org>,
	David Rientjes <rientjes@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Add overview and SLUB allocator sections to slab documentation
Date: Sat, 18 Apr 2026 13:20:42 +0200	[thread overview]
Message-ID: <75b2b254-2e02-43ca-9109-9812cf3f85b2@kernel.org> (raw)
In-Reply-To: <CABZAGRGCwM1PiSxennV-Uy9y1gGKjpcHeq+eOAbqSZcy3Qb55g@mail.gmail.com>

On 4/18/26 1:00 PM, Nick Huang wrote:
> Hi Lorenzo Stoakes
> Lorenzo Stoakes <ljs@kernel.org> 於 2026年4月18日週六 下午5:11寫道:
>>
>> On Sat, Apr 18, 2026 at 02:12:22PM +0800, Nick Huang wrote:
>>> Nick Huang <sef1548@gmail.com> 於 2026年4月18日週六 下午1:27寫道:
>>>>
>>>> Matthew Wilcox <willy@infradead.org> 於 2026年4月18日週六 下午1:04寫道:
>>>>>
>>>>> On Sat, Apr 18, 2026 at 12:06:19AM +0000, Nick Huang wrote:
>>>>>> - 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.
> 
> 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.



  reply	other threads:[~2026-04-18 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18  0:06 Nick Huang
2026-04-18  5:04 ` Matthew Wilcox
2026-04-18  5:27   ` Nick Huang
2026-04-18  6:12     ` Nick Huang
2026-04-18  9:11       ` Lorenzo Stoakes
2026-04-18 11:00         ` Nick Huang
2026-04-18 11:20           ` Vlastimil Babka (SUSE) [this message]
2026-04-18  6:19 ` Harry Yoo (Oracle)
2026-04-18  9:07 ` Lorenzo Stoakes

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=75b2b254-2e02-43ca-9109-9812cf3f85b2@kernel.org \
    --to=vbabka@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=hao.li@linux.dev \
    --cc=harry@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=rppt@kernel.org \
    --cc=sef1548@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox