[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0912020853320.31731@router.home>
Date: Wed, 2 Dec 2009 08:55:17 -0600 (CST)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Tejun Heo <tj@...nel.org>
cc: Ingo Molnar <mingo@...e.hu>,
Stephen Rothwell <sfr@...b.auug.org.au>,
michal.simek@...alogix.com, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: problems in linux-next (Was: Re: linux-next: Tree for December
1)
On Wed, 2 Dec 2009, Tejun Heo wrote:
> This isn't usual alignment. struct work_struct has one data fields
> which is overloaded for two purposes. Lower few bits are used to
> carry flags while upper bits are used to point to sruct
> cpu_workqueue_struct. So, the number of available bits for flags are
> determined by the alignment of cpu_workqueue_struct. Memory usage for
The default mininum slab alignment in UP is 8 bytes which means you can
use 3 bits. And as far as I can see only the lower two bits are used. You
still have one bit leftover. (current upstream that is did not check if
you modified it).
--
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