[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B023275.5000506@kernel.org>
Date: Tue, 17 Nov 2009 14:19:49 +0900
From: Tejun Heo <tj@...nel.org>
To: Rusty Russell <rusty@...tcorp.com.au>
CC: linux-kernel@...r.kernel.org, jeff@...zik.org, mingo@...e.hu,
akpm@...ux-foundation.org, jens.axboe@...cle.com,
cl@...ux-foundation.org, dhowells@...hat.com,
arjan@...ux.intel.com, torvalds@...ux-foundation.org,
avi@...hat.com, peterz@...radead.org, andi@...stfloor.org,
fweisbec@...il.com
Subject: Re: [PATCH 08/21] scheduler: implement force_cpus_allowed_ptr()
11/17/2009 02:14 PM, Rusty Russell wrote:
> On Tue, 17 Nov 2009 03:45:13 am Tejun Heo wrote:
>> Implement force_cpus_allowed_ptr() which is similar to
>> set_cpus_allowed_ptr() but bypasses PF_THREAD_BOUND check and ignores
>> cpu_active() status as long as the target cpu is online. This will be
>> used for concurrency-managed workqueue.
>
> Can we drop the silly _ptr() postfix? It was a hack someone added to
> avoid churning set_cpus_allowed(), and no need to repeat here.
Yeah, it's an ugly name. I'll drop it from the new function.
Thanks.
--
tejun
--
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