From: Konstantin Khlebnikov <koct9i@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
Leonard Crestez <lcrestez@ixiacom.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sorin Dumitru <sdumitru@ixiacom.com>
Subject: Re: [RFC v2] percpu: Add a separate function to merge free areas
Date: Fri, 5 Dec 2014 10:25:07 +0400 [thread overview]
Message-ID: <CALYGNiNioi3qaRy8VOSBshWtCBJc_qq4FRVVX85F+_aA6QtfKg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1412041520270.14925@gentwo.org>
On Fri, Dec 5, 2014 at 12:20 AM, Christoph Lameter <cl@linux.com> wrote:
> On Thu, 4 Dec 2014, Tejun Heo wrote:
>
>> Docker usage is pretty wide-spread now, making what used to be
>> siberia-cold paths hot enough to cause actual scalability issues.
>> Besides, we're now using percpu_ref for things like aio and cgroup
>> control structures which can be created and destroyed quite
>> frequently. I don't think we can say these are "weird" use cases
>> anymore.
>
> Well then lets write a scalable percpu allocator.
percpu allocator maybe be overkill but I think it's worth to make
kmem_cache-like thing with pool of objects.
>
> --
> 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>
--
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:[~2014-12-05 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 22:33 Leonard Crestez
2014-12-04 17:57 ` Tejun Heo
2014-12-04 20:10 ` Leonard Crestez
2014-12-04 20:28 ` Christoph Lameter
2014-12-04 20:45 ` Tejun Heo
2014-12-04 20:52 ` Al Viro
2014-12-04 21:15 ` Christoph Lameter
2014-12-04 21:19 ` Tejun Heo
2014-12-04 21:20 ` Christoph Lameter
2014-12-05 6:25 ` Konstantin Khlebnikov [this message]
2014-12-04 20:42 ` Tejun Heo
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=CALYGNiNioi3qaRy8VOSBshWtCBJc_qq4FRVVX85F+_aA6QtfKg@mail.gmail.com \
--to=koct9i@gmail.com \
--cc=cl@linux.com \
--cc=lcrestez@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sdumitru@ixiacom.com \
--cc=tj@kernel.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