From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Eric Dumazet <dada1@cosmosbay.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, "Zhang,
Yanmin" <yanmin_zhang@linux.intel.com>
Subject: Re: [PATCH] alloc_percpu() fails to allocate percpu data
Date: Mon, 3 Mar 2008 11:30:07 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0803031129330.7275@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200803031414.43076.nickpiggin@yahoo.com.au>
On Mon, 3 Mar 2008, Nick Piggin wrote:
> I think so. If we ask for HWCACHE_ALIGN, it must be for a good reason.
> If some structures get too bloated for no good reason, then the problem
> is not with the slab allocator but with the caller asking for
> HWCACHE_ALIGN.
Right. There should only be a few select users of this strange flag.
Otherwise if a certain alignment is wanted specify it in the alignment
parameter passed to kmem_cache_create.
next prev parent reply other threads:[~2008-03-03 19:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:00 [PATCH] alloc_percpu() fails to allocate percpu data Eric Dumazet
2008-02-21 22:26 ` Peter Zijlstra
2008-02-23 9:23 ` Nick Piggin
2008-02-27 19:44 ` Christoph Lameter
2008-03-03 3:14 ` Nick Piggin
2008-03-03 7:48 ` Eric Dumazet
2008-03-03 9:41 ` Nick Piggin
2008-03-03 19:30 ` Christoph Lameter [this message]
2008-02-23 8:04 ` Andrew Morton
2008-02-27 19:59 ` Christoph Lameter
2008-02-27 20:24 ` Andrew Morton
2008-02-27 21:56 ` Christoph Lameter
2008-03-01 13:53 ` Eric Dumazet
2008-03-11 18:15 ` Mike Snitzer
2008-03-11 18:41 ` Eric Dumazet
2008-03-11 19:39 ` Mike Snitzer
2008-03-12 0:18 ` [stable] " Chris Wright
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=Pine.LNX.4.64.0803031129330.7275@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=yanmin_zhang@linux.intel.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;
as well as URLs for NNTP newsgroup(s).