All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Matthew Wilcox <willy@infradead.org>,
	Jason Gunthorpe <jgg@ziepe.ca>, Jane Chu <jane.chu@oracle.com>,
	Muchun Song <songmuchun@bytedance.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>, Christoph Hellwig <hch@lst.de>,
	nvdimm@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [PATCH v8 3/5] mm/hugetlb_vmemmap: move comment block to Documentation/vm
Date: Thu, 10 Mar 2022 14:09:12 +0200	[thread overview]
Message-ID: <YinqaACBH7EvFQEn@kernel.org> (raw)
In-Reply-To: <1debf72b-8354-604e-1574-bf956c869dd7@oracle.com>

On Thu, Mar 10, 2022 at 11:32:21AM +0000, Joao Martins wrote:
> On 3/10/22 10:32, Mike Rapoport wrote:
> > Hi,
> > 
> > On Mon, Mar 07, 2022 at 12:24:55PM +0000, Joao Martins wrote:
> >> In preparation for device-dax for using hugetlbfs compound page tail
> >> deduplication technique, move the comment block explanation into a
> >> common place in Documentation/vm.
> >>
> >> Cc: Muchun Song <songmuchun@bytedance.com>
> >> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> >> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> >> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> >> Reviewed-by: Muchun Song <songmuchun@bytedance.com>
> >> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> >> ---
> >>  Documentation/vm/index.rst         |   1 +
> >>  Documentation/vm/vmemmap_dedup.rst | 173 +++++++++++++++++++++++++++++
> > 
> > Sorry for jumping late.
> > 
> > Please consider moving this into Documentation/vm/memory-model.rst along
> > with the documentation added in the next patch
> > 
> Hmmm, I don't think this is the right place to put it.
> 
> We don't change the memory model fundamentally (rather the *backing* pages of
> vmemmap VA in some specific cases) to justify putting the entire thing there.
> The new doc is also just as big as memory-model.rst doc. I feel the two separate
> docs stand on their own and the vmemmap dedup technique doc is better placed as
> its own.
> 
> Perhaps alternatively (in a followup patch) it could get a relevant mention
> (either in an new subsection or in paragraphs of the existing subsections)
> in memory-model.rst to point readers to vmemmap_dedup.rst...?

Sounds good to me.

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2022-03-10 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 12:24 [PATCH v8 0/5] sparse-vmemmap: memory savings for compound devmaps (device-dax) Joao Martins
2022-03-07 12:24 ` [PATCH v8 1/5] mm/sparse-vmemmap: add a pgmap argument to section activation Joao Martins
2022-03-07 12:24 ` [PATCH v8 2/5] mm/sparse-vmemmap: refactor core of vmemmap_populate_basepages() to helper Joao Martins
2022-03-07 12:24 ` [PATCH v8 3/5] mm/hugetlb_vmemmap: move comment block to Documentation/vm Joao Martins
2022-03-10 10:32   ` Mike Rapoport
2022-03-10 11:32     ` Joao Martins
2022-03-10 12:09       ` Mike Rapoport [this message]
2022-03-07 12:24 ` [PATCH v8 4/5] mm/sparse-vmemmap: improve memory savings for compound devmaps Joao Martins
2022-03-07 12:24 ` [PATCH v8 5/5] mm/page_alloc: reuse tail struct pages " Joao Martins

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=YinqaACBH7EvFQEn@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=jane.chu@oracle.com \
    --cc=jgg@ziepe.ca \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=songmuchun@bytedance.com \
    --cc=vishal.l.verma@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.