[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64003dcd-d954-b76d-856a-214ff11ac000@arm.com>
Date: Tue, 3 Sep 2019 17:31:46 +0100
From: Valentin Schneider <valentin.schneider@....com>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: mingo@...hat.com, peterz@...radead.org,
linux-kernel@...r.kernel.org, rcu@...r.kernel.org,
linux-block@...r.kernel.org, dm-devel@...hat.com, axboe@...nel.dk,
aarcange@...hat.com
Subject: Re: [PATCH] sched: make struct task_struct::state 32-bit
On 03/09/2019 17:23, Alexey Dobriyan wrote:
> On Tue, Sep 03, 2019 at 12:02:38AM +0100, Valentin Schneider wrote:
>> struct task_struct {
>> struct thread_info thread_info; /* 0 24 */
>> volatile int state; /* 24 4 */
>>
>> /* XXX 4 bytes hole, try to pack */
>>
>> void * stack; /* 32 8 */
>>
>> Though seeing as this is also the boundary of the randomized layout we can't
>> really do much better without changing the boundary itself. So much for
>> cacheline use :/
>
> Cacheline use of task_struct is pretty hopeless because of all the ifdefs.
>
Yeah I figured, then had a minute of silence for those forsaken bytes.
Powered by blists - more mailing lists