[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <486BE4EA.5030808@linux.intel.com>
Date: Wed, 02 Jul 2008 13:28:26 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
CC: Steven Rostedt <rostedt@...dmis.org>, benh@...nel.crashing.org,
ksummit-2008-discuss@...ts.linux-foundation.org,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Jeremy Kerr <jk@...abs.org>
Subject: Re: [Ksummit-2008-discuss] Delayed interrupt work, thread pools
James Bottomley wrote:
> Easier to implement, yes. Easier to program, unlikely, and coming with
> a large amount of overhead, definitely.
>
>> BTW, if something like this is implemented, I think that it should be a
>> replacement for softirqs and tasklets.
>
under the "better steal right (from other open source) than invent wrong" mantra:
it's worth looking at what glib does here; I've used their threadpools before and
it worked really well for me.... we could learn a lot from 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/
Powered by blists - more mailing lists