linux-kernel - Re: [RFC][PATCH 2/2] kernel: extract thread types from task

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20100920124143.a28b4c91.akpm@linux-foundation.org>
Date:	Mon, 20 Sep 2010 12:41:43 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	Tejun Heo <tj@...nel.org>, Avi Kivity <avi@...hat.com>
Subject: Re: [RFC][PATCH 2/2] kernel: extract thread types from
 task_struct::flags

On Mon, 20 Sep 2010 21:25:16 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> So can you agree with Linus' proposal of simply moving all type like
> bits over to a new word, or would you rather see the linear type field
> with an extra helper; possibly part of the existing ->flags field?

No strong feelings either way, really.

One thing we should keep an eye out for is the size/speed of code at
the client callsites.  Plucking a field of bits out of the flags word
and then treating that as a scalar would generate quite a bit of code,
I expect.  Let's not do that.
--
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/