Messages in this thread | | | Date | Thu, 22 Feb 2007 09:17:35 -0800 (PST) | Subject | Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 | From | David Miller <> |
| |
From: Ingo Molnar <mingo@elte.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |