From: Mike Rapoport <rppt@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: reorder memory-hotplug documentation
Date: Tue, 21 May 2019 19:00:40 +0300 [thread overview]
Message-ID: <20190521160040.GE24470@rapoport-lnx> (raw)
In-Reply-To: <43092504-a95f-374d-f3db-b961dd8ac428@redhat.com>
On Tue, May 21, 2019 at 12:41:50PM +0200, David Hildenbrand wrote:
> On 14.05.19 10:23, Mike Rapoport wrote:
> > The "Locking Internals" section of the memory-hotplug documentation is
> > duplicated in admin-guide and core-api. Drop the admin-guide copy as
> > locking internals does not belong there.
> >
> > While on it, move the "Future Work" section to the core-api part.
>
> Looks sane, but the future work part is really outdated, can we remove
> this completely?
>
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> > ---
> > +
> > +Future Work
> > +===========
> > +
> > + - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
> > + sysctl or new control file.
>
> ... that already works if I am not completely missing the point here
>
> > + - showing memory block and physical device relationship.
>
> ... that is available for s390x only AFAIK
>
> > + - test and make it better memory offlining.
>
> ... no big news ;)
>
> > + - support HugeTLB page migration and offlining.
>
> ... I remember that Oscar was doing something in that area, Oscar?
>
> > + - memmap removing at memory offline.
>
> ... no, we don't want this. However, we should properly clean up zone
> information when offlining
>
> > + - physical remove memory.
>
> ... I don't even understand what that means.
>
>
> I'd vote for removing the future work part, this is pretty outdated.
Frankly, I haven't looked at the details, just simply moved the text over.
I don't mind sending another mechanical patch that removes the future work
part.
But it would be far better if somebody who's actively working on memory
hotplug would replace it with a description how this actually works ;-)
> --
>
> Thanks,
>
> David / dhildenb
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-05-21 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 8:23 [PATCH] docs: reorder memory-hotplug documentation Mike Rapoport
2019-05-21 10:41 ` David Hildenbrand
2019-05-21 16:00 ` Mike Rapoport [this message]
2019-05-21 16:11 ` Oscar Salvador
2019-05-22 7:29 ` David Hildenbrand
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=20190521160040.GE24470@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).