[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091223075309.GF23839@elte.hu>
Date: Wed, 23 Dec 2009 08:53:09 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeff Garzik <jeff@...zik.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, awalls@...ix.net,
linux-kernel@...r.kernel.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
* Jeff Garzik <jeff@...zik.org> wrote:
> On 12/23/2009 01:02 AM, Ingo Molnar wrote:
> >One key thing i havent seen in this discussion are actual measurements. I
> >think a lot could be decided by simply testing this patch-set, by looking at
> >the hard numbers: how much faster (or slower) did a particular key workload
> >get before/after these patches.
>
> We are dealing with situations where drivers are using workqueues to
> provide a sleep-able context, and trying to solve problems related
> to that.
>
> "faster or slower?" is not very relevant for such cases.
Claims to performance were made though, so it's a valid question.
But it's not the only effect, which is why i continued my email with the issue
you raised:
> > Likewise, if there's a reduction in complexity, that is a tangible metric
> > as well: lets do a few conversions as part of the patch-set and see how
> > much simpler things have become as a result of it.
> >
> > We really are not forced to the space of Gedankenexperiments here.
Thanks,
Ingo
--
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