Re: [PATCH] Docs/mm: document Shared Memory Filesystem

["David Hildenbrand (arm)" <david@kernel.org>]

On 3/15/26 20:50, David Hildenbrand (arm) wrote:
> On 3/14/26 19:17, Andrew Morton wrote:
>> On Sat, 14 Mar 2026 17:02:47 +0100 Kit Dallege <xaum.io@gmail.com> wrote:
>>
>>> Hi Jon,
>>>
>>> The material was written with AI assistance (Claude) and then verified
>>> against the source code in mm/shmem.c. I read through the implementation,
>>> the existing comments, and Mel Gorman's book outline to identify what
>>> should be covered, then used AI to help draft the prose, which I reviewed
>>> and edited.
>>
>> OK, so you're saying that you created the content and used an LLM to
>> assist in finishing it off?
>>
>>> I'm happy to rework anything that's inaccurate or doesn't meet the bar.
>>> Should I add an Assisted-by tag to the commit?
>>
>> Yes, Assisted-by: is appropriate and useful here.
>>
>>   From a quick scan, this material appears to be helpful and I think it
>> would be good for us to get this into the tree in some fashion.  Which
>> will involve asking the relevant MM developers to review each change.
> 
> So, someone with an LLM but no proven experience with the code produced
> some doc, and maintainers/developers should dedicate their precious time
> to do the hard work of checking everything?
> 
> I'm all for documenting stuff, especially if newcomers start exploring
> that space by contributing small, carefully crafted documentation updates.
> 
> It's then a good learning experience for someone that wants to work on
> the code to really have to understand the code in detail, and what is
> actually worth documenting (and what's an implementation detail).
> 
> I see 7 doc updates for 7 different MM subsystems in my inbox, including

... "the buddy, and for example, no mentioning of the pcp, but for some 
reason page isolation instead."


-- 
Cheers,

David