From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] percpu changes for v3.15-rc1
Date: Mon, 31 Mar 2014 14:58:17 -0400 [thread overview]
Message-ID: <20140331185817.GA28901@mtj.dyndns.org> (raw)
Hello, Linus.
percpu allocation is now popular enough for the extremely naive range
allocator to cause scalability issues. The existing allocator
linearly scanned the allocation map on both alloc and free without
making use of hint or anything. Al reimplemented the range allocator
so that it can use binary search instead of linear scan during free
and alloc path uses simple hinting to avoid scanning in common cases.
Combined, the new allocator resolves the scalability issue percpu
allocator was showing during container benchmark workload.
The following changes since commit 0f0ca14386e0431fbedaae5efc550d46cf93b9cf:
Merge tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (2014-02-22 08:29:25 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-3.15
for you to fetch changes up to 21ddfd38ee9aac804d22beaceed4c7b903cca234:
percpu: renew the max_contig if we merge the head and previous block (2014-03-29 09:29:42 -0400)
Thanks.
----------------------------------------------------------------
Al Viro (4):
perpcu: fold pcpu_split_block() into the only caller
percpu: store offsets instead of lengths in ->map[]
percpu: speed alloc_pcpu_area() up
percpu: allocation size should be even
Jianyu Zhan (1):
percpu: renew the max_contig if we merge the head and previous block
mm/percpu.c | 208 ++++++++++++++++++++++++++++++++----------------------------
1 file changed, 112 insertions(+), 96 deletions(-)
--
tejun
reply other threads:[~2014-03-31 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140331185817.GA28901@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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®