From: Tejun Heo <tj@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Leonard Crestez <lcrestez@ixiacom.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sorin Dumitru <sdumitru@ixiacom.com>
Subject: Re: [RFC v2] percpu: Add a separate function to merge free areas
Date: Thu, 4 Dec 2014 15:45:34 -0500 [thread overview]
Message-ID: <20141204204534.GE4080@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1412041426230.14577@gentwo.org>
Hello, Christoph.
On Thu, Dec 04, 2014 at 02:28:10PM -0600, Christoph Lameter wrote:
> Well this is not a common use case and that is not what the per cpu
> allocator was designed for. There is bound to be signifcant fragmentation
> with the current design. The design was for rare allocations when
> structures are initialized.
My unverified gut feeling is that fragmentation prolly is a lot less
of a problem for percpu allocator given that most percpu allocations
are fairly small. On the other hand, we do wanna pack them tight as
percpu memory is really expensive space-wise. I could be wrong tho.
Thanks.
--
tejun
--
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-04 20:45 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 [this message]
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
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=20141204204534.GE4080@htj.dyndns.org \
--to=tj@kernel.org \
--cc=cl@linux.com \
--cc=lcrestez@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sdumitru@ixiacom.com \
/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