[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FCFEFF0.5070108@zytor.com>
Date: Wed, 06 Jun 2012 17:04:00 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Thomas Gleixner <tglx@...utronix.de>,
Rusty Russell <rusty@...tcorp.com.au>,
Fenghua Yu <fenghua.yu@...el.com>, Ingo Molnar <mingo@...e.hu>,
Suresh B Siddha <suresh.b.siddha@...el.com>,
Tony Luck <tony.luck@...el.com>,
Asit K Mallick <asit.k.mallick@...el.com>,
Arjan Dan De Ven <arjan@...ux.intel.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
x86 <x86@...nel.org>, linux-pm <linux-pm@...r.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: [PATCH] kthread: Implement park/unpark facility
On 06/05/2012 07:05 AM, Peter Zijlstra wrote:
> On Tue, 2012-06-05 at 15:41 +0200, Thomas Gleixner wrote:
>> struct kthread {
>> - int should_stop;
>> + bool should_stop;
>> + bool should_park;
>> + bool is_parked;
>> + bool is_percpu;
>
> bool doesn't have a well specified storage type. I typically try to
> avoid using it in structures for this reason. Others might not care
> though.
>
On all known Linux platforms, bool is implemented as a single byte
having a value of either 0 or 1. However, it might make more sense to
have a flags field here...
-hpa
--
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