From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: steven.sistare@oracle.com, daniel.m.jordan@oracle.com,
mgorman@techsingularity.net, mhocko@suse.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
vbabka@suse.cz, bharata@linux.vnet.ibm.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
dan.j.williams@intel.com, kirill.shutemov@linux.intel.com,
bhe@redhat.com
Subject: Re: [PATCH v3 0/4] optimize memory hotplug
Date: Tue, 13 Feb 2018 13:53:59 -0800 [thread overview]
Message-ID: <20180213135359.705680d373a482b650f38b50@linux-foundation.org> (raw)
In-Reply-To: <20180213193159.14606-1-pasha.tatashin@oracle.com>
On Tue, 13 Feb 2018 14:31:55 -0500 Pavel Tatashin <pasha.tatashin@oracle.com> wrote:
> This patchset:
> - Improves hotplug performance by eliminating a number of
> struct page traverses during memory hotplug.
>
> - Fixes some issues with hotplugging, where boundaries
> were not properly checked. And on x86 block size was not properly aligned
> with end of memory
>
> - Also, potentially improves boot performance by eliminating condition from
> __init_single_page().
>
> - Adds robustness by verifying that that struct pages are correctly
> poisoned when flags are accessed.
I'm now attempting to get a 100% review rate on MM patches, which is
why I started adding my Reviewed-by: when I do that thing.
I'm not familiar enough with this code to add my own Reviewed-by:, and
we'll need to figure out what to do in such cases. I shall be sending
out periodic review-status summaries.
If you're able to identify a suitable reviewer for this work and to
offer them beer, that would help. Let's see what happens as the weeks
unfold.
next prev parent reply other threads:[~2018-02-13 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:31 Pavel Tatashin
2018-02-13 19:31 ` [PATCH v3 1/4] mm/memory_hotplug: enforce block size aligned range check Pavel Tatashin
2018-02-15 11:34 ` Michal Hocko
2018-02-15 13:36 ` Pavel Tatashin
2018-02-15 14:40 ` Michal Hocko
2018-02-15 15:05 ` Pavel Tatashin
2018-02-13 19:31 ` [PATCH v3 2/4] x86/mm/memory_hotplug: determine block size based on the end of boot memory Pavel Tatashin
2018-02-15 11:37 ` Michal Hocko
2018-02-15 13:39 ` Pavel Tatashin
2018-02-15 19:00 ` Ingo Molnar
2018-02-13 19:31 ` [PATCH v3 3/4] mm: uninitialized struct page poisoning sanity checking Pavel Tatashin
2018-02-15 11:53 ` Michal Hocko
2018-02-15 13:41 ` Pavel Tatashin
2018-02-13 19:31 ` [PATCH v3 4/4] mm/memory_hotplug: optimize memory hotplug Pavel Tatashin
2018-02-15 12:43 ` Michal Hocko
2018-02-15 13:46 ` Pavel Tatashin
2018-02-13 21:53 ` Andrew Morton [this message]
2018-02-14 8:09 ` [PATCH v3 0/4] " Ingo Molnar
2018-02-14 14:14 ` Pavel Tatashin
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=20180213135359.705680d373a482b650f38b50@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.m.jordan@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®