From: Christoph Lameter <cl@linux.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Linux-MM <linux-mm@kvack.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7
Date: Wed, 7 Dec 2016 08:52:27 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1612070849260.8398@east.gentwo.org> (raw)
In-Reply-To: <20161207101228.8128-1-mgorman@techsingularity.net>
On Wed, 7 Dec 2016, Mel Gorman wrote:
> SLUB has been the default small kernel object allocator for quite some time
> but it is not universally used due to performance concerns and a reliance
> on high-order pages. The high-order concerns has two major components --
SLUB does not rely on high order pages. It falls back to lower order if
the higher orders are not available. Its a performance concern.
This is also an issue for various other kernel subsystems that really
would like to have larger contiguous memory area. We are often seeing
performance constraints due to the high number of 4k segments when doing
large scale block I/O f.e.
Otherwise I really like what I am seeing here.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-07 14:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 10:12 Mel Gorman
2016-12-07 14:52 ` Christoph Lameter [this message]
2016-12-07 15:57 ` Mel Gorman
2016-12-07 16:40 ` Christoph Lameter
2016-12-07 16:45 ` Mel Gorman
2016-12-07 17:11 ` Christoph Lameter
2016-12-07 17:35 ` Mel Gorman
2016-12-07 19:00 ` Eric Dumazet
2016-12-07 19:11 ` Eric Dumazet
2016-12-07 19:48 ` Mel Gorman
2016-12-07 20:10 ` Eric Dumazet
2016-12-07 21:19 ` Mel Gorman
2016-12-07 23:25 ` Mel Gorman
2016-12-08 8:22 ` Jesper Dangaard Brouer
2016-12-08 9:18 ` Mel Gorman
2016-12-08 10:43 ` Jesper Dangaard Brouer
2016-12-08 11:06 ` Mel Gorman
2016-12-08 14:48 ` Jesper Dangaard Brouer
2016-12-08 15:11 ` Mel Gorman
2016-12-08 17:19 ` Jesper Dangaard Brouer
2016-12-08 17:39 ` Mel Gorman
2016-12-08 16:04 ` Eric Dumazet
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=alpine.DEB.2.20.1612070849260.8398@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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