[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060726084921.GB9592@osiris.boeblingen.de.ibm.com>
Date: Wed, 26 Jul 2006 10:49:21 +0200
From: Heiko Carstens <heiko.carstens@...ibm.com>
To: Christoph Lameter <clameter@....com>
Cc: Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [patch] slab: always follow arch requested alignments
On Sun, Jul 23, 2006 at 06:24:27PM +0200, Heiko Carstens wrote:
> On Sun, Jul 23, 2006 at 06:03:09AM -0700, Christoph Lameter wrote:
> > On Sun, 23 Jul 2006, Heiko Carstens wrote:
> > > > See kmem_cache_create():
> > > > /* 2) arch mandated alignment: disables debug if necessary */
> > > > if (ralign < ARCH_SLAB_MINALIGN) {
> > > > ralign = ARCH_SLAB_MINALIGN;
> > > > if (ralign > BYTES_PER_WORD)
> > > > flags &= ~(SLAB_RED_ZONE | SLAB_STORE_USER);
> > > > }
> > >
> > > That is because if kmem_cache_create gets called with SLAB_HWCACHE_ALIGN set
> > > in flags then ralign will be greater or equal to ARCH_SLAB_MINALIGN:
> > >
> > > /* 1) arch recommendation: can be overridden for debug */
> > > if (flags & SLAB_HWCACHE_ALIGN) {
> > > [...]
> > > ralign = cache_line_size();
> > > [...]
> >
> > Ok. Then you do not have a problem because ralign is greater than
> > ARCH_SLAB_MINALIGN.
> >
> > > Therefore the test above will be passed and SLAB_RED_ZONE and SLAB_STORE_USER
> > > will stay in flags.
> > > cache_line_size() will return 256 on s390.
> >
> > Looks as if you would have the correct alignment then. I still do not
> > understand where the problem is since you want to align on an 8 byte
> > boundary.
>
> CONFIG_DEBUG_SLAB is on. In step 4) we have align = ralign.
> Still ok.
> Next thing:
>
> if (flags & SLAB_RED_ZONE) {
> /* redzoning only works with word aligned caches */
> align = BYTES_PER_WORD;
>
> Result: align is less than ARCH_SLAB_MINALIGN -> busted.
> Same is true if SLAB_STORE_USER is set.
> Therefore I masked them both out in my patch.
Since I didn't get an ACK or NACK, I split this patch into two very small
ones and repost them. Hopefully with a better description than the first
time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists