From: "Zi Yan" <zi.yan@cs.rutgers.edu>
To: Christopher Lameter <cl@linux.com>
Cc: Thomas Schoebel-Theuer <tst@schoebel-theuer.de>,
Mel Gorman <mgorman@techsingularity.net>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-rdma@vger.kernel.org,
akpm@linux-foundation.org, andi@firstfloor.org,
Rik van Riel <riel@redhat.com>, Michal Hocko <mhocko@kernel.org>,
Guy Shattah <sguy@mellanox.com>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Michal Nazarewicz <mina86@mina86.com>,
Vlastimil Babka <vbabka@suse.cz>,
David Nellans <dnellans@nvidia.com>,
Laura Abbott <labbott@redhat.com>, Pavel Machek <pavel@ucw.cz>,
Dave Hansen <dave.hansen@intel.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [RFC 1/2] Protect larger order pages from breaking up
Date: Thu, 22 Feb 2018 21:16:07 -0500 [thread overview]
Message-ID: <1B85435E-A9FB-47E7-A2FE-FE21632778F0@cs.rutgers.edu> (raw)
In-Reply-To: <alpine.DEB.2.20.1802222000470.2221@nuc-kabylake>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
Yes. I saw the attached patches. I am definitely going to apply them and see how they work out.
In his last patch, there are a bunch of magic numbers used to reserve free page blocks
at different orders. I think that is the most interesting part. If Thomas can share how
to determine these numbers with his theory based on workloads, hardware/chipset, that would
be a great guideline for sysadmins to take advantage of the patches.
—
Best Regards,
Yan Zi
On 22 Feb 2018, at 21:01, Christopher Lameter wrote:
> On Thu, 22 Feb 2018, Zi Yan wrote:
>
>> I am very interested in the theory behind your patch. Do you mind sharing it? Is there
>> any required math background before reading it? Is there any related papers/articles I could
>> also read?
>
> His patches were attached to the email you responded to. Guess I should
> update the patchset with the suggested changes and repost.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 557 bytes --]
next prev parent reply other threads:[~2018-02-23 2:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:01 [RFC 0/2] Larger Order Protection V1 Christoph Lameter
2018-02-16 16:01 ` [RFC 1/2] Protect larger order pages from breaking up Christoph Lameter
2018-02-16 17:03 ` Andi Kleen
2018-02-16 18:25 ` Christopher Lameter
2018-02-16 18:02 ` Randy Dunlap
2018-02-17 16:07 ` Mike Rapoprt
2018-02-16 18:59 ` Mike Kravetz
2018-02-16 20:13 ` Christopher Lameter
2018-02-18 9:00 ` Guy Shattah
2018-02-16 19:01 ` Dave Hansen
2018-02-16 20:15 ` Christopher Lameter
2018-02-16 21:08 ` Dave Hansen
2018-02-16 21:43 ` Matthew Wilcox
2018-02-16 21:47 ` Dave Hansen
2018-02-19 10:19 ` Mel Gorman
2018-02-19 14:42 ` Michal Hocko
2018-02-19 15:09 ` Christopher Lameter
2018-02-22 21:19 ` Thomas Schoebel-Theuer
2018-02-22 21:53 ` Zi Yan
2018-02-23 2:01 ` Christopher Lameter
2018-02-23 2:16 ` Zi Yan [this message]
2018-02-23 2:45 ` Christopher Lameter
2018-02-23 9:59 ` Mel Gorman
2018-02-16 16:01 ` [RFC 2/2] Page order diagnostics Christoph Lameter
2018-02-17 21:17 ` Pavel Machek
2018-02-19 14:54 ` Christopher Lameter
2018-02-16 18:27 ` [RFC 0/2] Larger Order Protection V1 Christopher Lameter
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=1B85435E-A9FB-47E7-A2FE-FE21632778F0@cs.rutgers.edu \
--to=zi.yan@cs.rutgers.edu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux.com \
--cc=dave.hansen@intel.com \
--cc=dnellans@nvidia.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=labbott@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mina86@mina86.com \
--cc=pavel@ucw.cz \
--cc=riel@redhat.com \
--cc=sguy@mellanox.com \
--cc=tst@schoebel-theuer.de \
--cc=vbabka@suse.cz \
--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