[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B31D99D.4070705@kernel.org>
Date: Wed, 23 Dec 2009 17:49:33 +0900
From: Tejun Heo <tj@...nel.org>
To: Ingo Molnar <mingo@...e.hu>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>, awalls@...ix.net,
linux-kernel@...r.kernel.org, jeff@...zik.org,
akpm@...ux-foundation.org, jens.axboe@...cle.com,
rusty@...tcorp.com.au, cl@...ux-foundation.org,
dhowells@...hat.com, arjan@...ux.intel.com, avi@...hat.com,
johannes@...solutions.net, andi@...stfloor.org
Subject: Re: workqueue thing
Hello,
On 12/23/2009 05:37 PM, Ingo Molnar wrote:
>> Sure, fair enough but there's also a different side. It'll allow much
>> easier implementation of things like in-kernel media presence polling (I
>> have some code for this but it's still just forming) and per-device. It
>> gives a much easier tool to extract concurrency and thus opens up new
>> possibilities.
>>
>> So, anyways, alright, I'll go try some conversions.
>
> Well, but note that you are again talking performance. Concurrency
> _IS_ performance: either in terms of reduced IO/app/request latency
> or in terms of CPU utilization.
I wasn't talking about performance above. Easiness or flexibility to
extract concurrency opens up possibilities for new things or easier
ways of doing things. It affects the design process. You don't have
to jump through hoops for concurrency management and removing that
restriction results in lower amount of convolution and simplifies
design.
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