From: Matt Mackall <mpm@selenic.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, "David S. Miller" <davem@davemloft.net>,
netfilter@vger.kernel.org
Subject: Re: [PATCH] slob: push the min alignment to long long
Date: Wed, 15 Jun 2011 15:24:26 -0500 [thread overview]
Message-ID: <1308169466.15617.378.camel@calx> (raw)
In-Reply-To: <20110615201202.GB19593@Chamillionaire.breakpoint.cc>
On Wed, 2011-06-15 at 22:12 +0200, Sebastian Andrzej Siewior wrote:
> * Matt Mackall | 2011-06-14 17:05:40 [-0500]:
>
> >Ok, so you claim that ARCH_KMALLOC_MINALIGN is not set on some
> >architectures, and thus SLOB does the wrong thing.
> >
> >Doesn't that rather obviously mean that the affected architectures
> >should define ARCH_KMALLOC_MINALIGN? Because, well, they have an
> >"architecture-specific minimum kmalloc alignment"?
>
> nope, if nothing is defined SLOB asumes that alignment of long is the way
> go. Unfortunately alignment of u64 maybe larger than of u32.
I understand that. I guess we have a different idea of what constitutes
"architecture-specific" and what constitutes "normal".
But I guess I can be persuaded that most architectures now expect 64-bit
alignment of u64s.
--
Mathematics is the supreme nostalgia of our time.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-15 20:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 20:10 [PATCH] slob: push the min alignment to long long Sebastian Andrzej Siewior
2011-06-14 20:10 ` Sebastian Andrzej Siewior
2011-06-14 20:40 ` Christoph Lameter
2011-06-14 21:16 ` Christoph Lameter
2011-06-15 20:06 ` Sebastian Andrzej Siewior
2011-06-16 16:48 ` Pekka Enberg
2011-06-22 23:41 ` David Rientjes
2011-06-22 23:41 ` David Rientjes
2011-06-23 14:36 ` Christoph Lameter
2011-06-23 14:36 ` Christoph Lameter
2011-06-23 20:24 ` David Rientjes
2011-06-14 22:05 ` Matt Mackall
2011-06-15 20:12 ` Sebastian Andrzej Siewior
2011-06-15 20:24 ` Matt Mackall [this message]
2011-06-15 20:40 ` Pekka Enberg
2011-06-15 20:55 ` Matt Mackall
2011-06-15 22:11 ` David Miller
2011-06-15 22:53 ` Matt Mackall
2011-06-16 6:59 ` Pekka Enberg
2011-06-16 6:59 ` Pekka Enberg
2011-06-16 15:23 ` Matt Mackall
2011-06-16 15:28 ` Pekka Enberg
2011-06-15 22:08 ` David Miller
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=1308169466.15617.378.camel@calx \
--to=mpm@selenic.com \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=netfilter@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sebastian@breakpoint.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.