[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070222.091735.30182079.davem@davemloft.net>
Date: Thu, 22 Feb 2007 09:17:35 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: mingo@...e.hu
Cc: johnpol@....mipt.ru, arjan@...radead.org, drepper@...hat.com,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
hch@...radead.org, akpm@....com.au, alan@...rguk.ukuu.org.uk,
zach.brown@...cle.com, suparna@...ibm.com, davidel@...ilserver.org,
jens.axboe@...cle.com, tglx@...utronix.de
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
From: Ingo Molnar <mingo@...e.hu>
Date: Thu, 22 Feb 2007 16:15:09 +0100
> furthermore, in a real webserver there's a whole lot of other stuff
> happening too: VFS blocking, mutex/lock blocking, memory pressure
> blocking, filesystem blocking, etc., etc. Threadlets/syslets cover them
> /all/ and never hold up the primary context: as long as there's more
> requests to process, they will be processed. Plus other important
> networked workloads, like fileservers are typically on fast LANs and
> those requests are very much a fire-and-forget matter most of the time.
I expect clients of a fileserver to cause the server to block in
places such as tcp_sendmsg() as much if not more so than a webserver
:-)
But yes, it should all be tested, for sure.
-
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