linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Michal Hocko <mhocko@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Oscar Salvador <osalvador@suse.de>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Mike Rapoport <rppt@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Matthew Wilcox <willy@infradead.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Muchun Song <songmuchun@bytedance.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v1] memory-hotplug.rst: complete admin-guide overhaul
Date: Mon, 7 Jun 2021 10:08:59 +0200	[thread overview]
Message-ID: <14b018b0-aa19-7d00-2861-50d0e5e2bea8@redhat.com> (raw)
In-Reply-To: <YL3QApMe/9R/xfLU@dhcp22.suse.cz>

On 07.06.21 09:51, Michal Hocko wrote:
> [Sorry this somehow slipped through cracks]
> 
> On Tue 25-05-21 12:26:04, David Hildenbrand wrote:
>> The memory hot(un)plug documentation is outdated and incomplete. Most of
>> the content dates back to 2007, so it's time for a major overhaul.
>>
>> Let's rewrite, reorganize and update most parts of the documentation. In
>> addition to memory hot(un)plug, also add some details regarding
>> ZONE_MOVABLE, with memory hotunplug being one of its main consumers.
>>
>> The style of the document is also properly fixed that e.g., "restview"
>> renders it cleanly now.
>>
>> In the future, we might add some more details about virt users like
>> virtio-mem, the XEN balloon, the Hyper-V balloon and ppc64 dlpar.
> 
> I haven't really checked the diff but rather looked at the final
> outcome. I have to say I like it a lot. Some places are going a bit too
> technical for an admin-guide but they are in minority (e.g. locking or
> altmap reference). If somebody feels strong then this could get into its
> own file but I wouldn't lose sleep over that.

I just realized that "Locking Internals" is still a duplicate with 
core-api/memory-hotplug.rst

I thought this (merge issue) was fixed long ago. I'll just remove it 
from this file, making sure core-api/memory-hotplug.rst is up-to-date

> 
> I would make one thing slightly more explicit though
> diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
> index c95f5c2b30dd..5b462aba89cc 100644
> --- a/Documentation/admin-guide/mm/memory-hotplug.rst
> +++ b/Documentation/admin-guide/mm/memory-hotplug.rst
> @@ -568,6 +568,10 @@ Even with ZONE_MOVABLE, there are some corner cases where offlining a memory
>   Further, when running into out of memory situations while migrating pages, or
>   when still encountering permanently unmovable pages within ZONE_MOVABLE
>   (-> BUG), memory offlining will keep retrying until it eventually succeeds.
> +The offlining context can be terminated by a fatal signal. A timeout based
> +offlining can be easily implemented by
> +
> +        % timeout $TIMEOUT offline_block | failure_handling
>   
>   Locking Internals
>   =================
> 
> 
> In the future I would find some examples of a failure cases we have seen
> so far. E.g. offlining failure with dump_page example.


Thanks, I'll pick up your change and see if I can get rid of some 
low-level stuff. I'll address Mike's review shortly and resend.

-- 
Thanks,

David / dhildenb


  reply	other threads:[~2021-06-07  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 10:26 [PATCH v1] memory-hotplug.rst: complete admin-guide overhaul David Hildenbrand
2021-05-26  6:54 ` Mike Rapoport
2021-06-08 12:05   ` David Hildenbrand
2021-06-08 14:16     ` Mike Rapoport
2021-06-08 15:22       ` David Hildenbrand
2021-06-07  7:51 ` Michal Hocko
2021-06-07  8:08   ` David Hildenbrand [this message]
2021-06-07 11:35 ` Mike Rapoport
2021-06-08 13:04   ` David Hildenbrand
2021-06-08 14:18     ` Mike Rapoport

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=14b018b0-aa19-7d00-2861-50d0e5e2bea8@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=osalvador@suse.de \
    --cc=pasha.tatashin@soleen.com \
    --cc=rppt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=songmuchun@bytedance.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;
as well as URLs for NNTP newsgroup(s).