From: "Zi Yan" <zi.yan@cs.rutgers.edu>
To: Thomas Schoebel-Theuer <tst@schoebel-theuer.de>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Christoph Lameter <cl@linux.com>,
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 16:53:25 -0500 [thread overview]
Message-ID: <E4FA7972-B97C-4D63-8473-C6F1F4FAB7A0@cs.rutgers.edu> (raw)
In-Reply-To: <68050f0f-14ca-d974-9cf4-19694a2244b9@schoebel-theuer.de>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
On 22 Feb 2018, at 16:19, Thomas Schoebel-Theuer wrote:
<snip>
>
> No need for a deep understanding of the theory of the memory fragmentation problem.
>
> Also no need for adding anything to the boot commandline. Fragmentation will typically occur only after some days or weeks or months of operation, at least in all of the practical cases I have personally seen at 1&1 datacenters and their workloads.
>
> Please notice that fragmentation can be a very serious problem for operations if you are hurt by it. It can seriously harm your business. And it is _extremely_ specific to the actual workload, and to the hardware / chipset / etc. This is addressed by the above method of determining the right values from _actual_ operations (not from speculation) and then memoizing them.
>
> The attached patchset tries to be very simple, but in my practical experience it is a very effective practical solution.
>
> When requested, I can post the mathematical theory behind the patch, or I could give a presentation at some of the next conferences if I would be invited (or better give a practical explanation instead). But probably nobody on these lists wants to deal with any theories.
Hi Thomas,
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?
Thanks.
--
Best Regards
Yan Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2018-02-22 21:53 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 [this message]
2018-02-23 2:01 ` Christopher Lameter
2018-02-23 2:16 ` Zi Yan
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=E4FA7972-B97C-4D63-8473-C6F1F4FAB7A0@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