From: SeongJae Park <sj@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: [PATCH 4/4] Docs/mm/index: move allocation profiling document to unsorted documents chapter
Date: Wed, 3 Jul 2024 20:33:05 -0700 [thread overview]
Message-ID: <20240704033305.93425-1-sj@kernel.org> (raw)
In-Reply-To: <CAJuCfpFO_C_LgxrRWrxG9o==RRtYAbkbP3ZJULwdmTjDcAJNrg@mail.gmail.com>
On Wed, 3 Jul 2024 19:10:03 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
> On Wed, Jul 3, 2024 at 4:00 PM SeongJae Park <sj@kernel.org> wrote:
> >
> > On Wed, 03 Jul 2024 16:18:42 -0600 Jonathan Corbet <corbet@lwn.net> wrote:
> >
> > > SeongJae Park <sj@kernel.org> writes:
> > >
> > > > The memory allocation profiling document was added to the bottom of the
> > > > new outline. Apparently it was not decided by well-defined guidelines
> > > > or a thorough discussions. Rather than that, it was added there just
> > > > because there was no place for such unsorted documents. Now there is
> > > > the chapter. Move the document to the new place.
> > >
> > > I'll take this for now, but it's truly sad to see new documentation
> > > being added to the slushpile at the end. It seems better to create a
> > > "development tools" section in the new outline and put the allocation
> > > profiling document there?
> >
> > I have no strong opinions about that. Cc-ing Suren and Kent, as they are the
> > author of the allocation profiling document and hence might have some opinion.
>
> IMHO if this would be the only document belonging to "development
> tools" then keeping it under unsorted is fine.
> If more documents will fall into that category then Jonathan's
> suggestion makes sense to me. Looking at the current list, page_owner
> and maybe damon might be considered for this category as well.
> SeongJae, WDYT?
I agree it makes more sense to have multiple documents under dedicated
sections. And putting page_owner sounds not that odd to me.
DAMON is, however, not a tool but a framework that helps easy development of
access-aware kernel components. Such components could be development tools and
system operations optimizations (using DAMOS). So, IMHO, 'development tools'
section is not the perfect place for DAMON documents.
Actually, even for allocation-profiling and page_owner, I think 'development
tools' might not be a perfect category. I understand those as features that
could be useful for system investigations of multiple purposes.
So, in short, I think it is not easy to find a perfect cateogry...
Thanks,
SJ
[...]
next prev parent reply other threads:[~2024-07-04 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 19:05 [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs SeongJae Park
2024-07-01 19:05 ` [PATCH 1/4] Docs/mm/allocation-profiling: mark 'Theory of operation' as chapter SeongJae Park
2024-07-01 21:29 ` Suren Baghdasaryan
2024-07-01 19:05 ` [PATCH 2/4] Docs/mm/index: Remove 'Memory Management Guide' chapter marker SeongJae Park
2024-07-01 19:05 ` [PATCH 3/4] Docs/mm/index: rename 'Legacy Documentation' to 'Unsorted Documentation' SeongJae Park
2024-07-01 19:05 ` [PATCH 4/4] Docs/mm/index: move allocation profiling document to unsorted documents chapter SeongJae Park
2024-07-03 22:18 ` Jonathan Corbet
2024-07-03 23:00 ` SeongJae Park
[not found] ` <CAJuCfpFO_C_LgxrRWrxG9o==RRtYAbkbP3ZJULwdmTjDcAJNrg@mail.gmail.com>
2024-07-04 2:18 ` Randy Dunlap
2024-07-04 2:36 ` Suren Baghdasaryan
2024-07-04 3:33 ` SeongJae Park [this message]
2024-07-03 22:20 ` [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs Jonathan Corbet
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=20240704033305.93425-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
/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;
as well as URLs for NNTP newsgroup(s).