Re: [PATCH v4.4-rc7] sched: isolate task_struct bitfields according to synchronization domains

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 30, 2015 at 1:23 AM, Tejun Heo <tj@xxxxxxxxxx> wrote:
>
> Peter, I took the patch and changed the bitfields to ulong.

I wouldn't expect the unsigned long part to matter, except for the
forced split with

   unsigned long :0;

itself.

Also, quite frankly, since this is basically very close to other
fields that are *not* unsigned longs, I'd really prefer to not
unnecessarily use a 64-bit field for three bits each.

So why not just do it with plain unsigned "int", and then maybe just
intersperse them with the other int-sized fields in that neighborhood.

I'm also wondering if we shouldn't just put the scheduler bits in the
"atomic_flags" thing instead?

                     Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]