From: David Rientjes <rientjes@google.com>
To: George Spelvin <linux@horizon.com>
Cc: herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mpm@selenic.com,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 5/8] mm/slub: Factor out some common code.
Date: Wed, 16 Mar 2011 14:51:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1103161352150.11002@chino.kir.corp.google.com> (raw)
In-Reply-To: <20110316205139.2035.qmail@science.horizon.com>
On Wed, 16 Mar 2011, George Spelvin wrote:
> > 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.)
>
Patches that you would like to propose but don't think are ready for merge
should have s/PATCH/RFC/ done on the subject line.
> > 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:
>
You deliberately created a helper function to take an unsigned int when
the actuals being passed in are all unsigned long to trigger a discussion
on why they are unsigned long?
> *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.)
>
unsigned long uses the native word size of the architecture which can
generate more efficient code; we typically imply that flags have a limited
size by including leading zeros in their definition for 32-bit
compatibility:
#define SLAB_DEBUG_FREE 0x00000100UL /* DEBUG: Perform (expensive) checks on free */
#define SLAB_RED_ZONE 0x00000400UL /* DEBUG: Red zone objs in a cache */
#define SLAB_POISON 0x00000800UL /* DEBUG: Poison 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/ .
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 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 1:58 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
2011-03-16 21:51 ` David Rientjes [this message]
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=alpine.DEB.2.00.1103161352150.11002@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@horizon.com \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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