From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, rientjes@google.com
Cc: herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mpm@selenic.com, penberg@cs.helsinki.fi
Subject: Re: [PATCH 5/8] mm/slub: Factor out some common code.
Date: 16 Mar 2011 16:51:39 -0400 [thread overview]
Message-ID: <20110316205139.2035.qmail@science.horizon.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103161308410.11002@chino.kir.corp.google.com>
> Where's your signed-off-by?
Somewhere under the pile of crap on my desk. :-)
(More to the point, waiting for me to think it's good enough to submit
For Real.)
> Nice cleanup.
>
> "flag" should be unsigned long in all of these functions: the constants
> are declared with UL suffixes in slab.h.
Actually, I did that deliberately. Because there's a problem I keep
wondering about, which repeats many many times in the kernel:
*Why* are they unsigned long? That's an awkward type: 32 bits on many
architectures, so we can't portably assign more than 32 bits, and on
platforms where it's 64 bits, the upper 32 are just wasting space.
(And REX prefixes on x86-64.)
Wouldn't it be a better cleanup to convert the whole lot to unsigned
or u32?
--
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-03-16 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 1:58 [PATCH 5/8] mm/slub: Factor out some common code George Spelvin
2011-03-16 3:12 ` Matt Mackall
2011-03-16 6:32 ` Pekka Enberg
2011-03-16 20:28 ` David Rientjes
2011-03-16 20:51 ` George Spelvin [this message]
2011-03-16 21:51 ` David Rientjes
2011-03-16 22:36 ` George Spelvin
2011-03-17 6:23 ` Pekka Enberg
2011-03-17 7:07 ` George Spelvin
2011-03-17 8:01 ` Pekka Enberg
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=20110316205139.2035.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.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).