| |||||||||||||
ExokernelsExokernelsPosted Feb 2, 2006 4:11 UTC (Thu) by ttfkam (guest, #29791)Parent article: Van Jacobson's network channels Reading about moving the network stack out to userspace made me think of the design of MIT's Exokernel OS. Just as Ingo Molnar's work in migrating the scheduler to an O(1) algorithm was a taste of more extensive implementation of O(1) algorithms in the kernel, perhaps elements of the exokernel will find their day in various parts of Linux.
(Log in to post comments)
Exokernels Posted Feb 2, 2006 11:55 UTC (Thu) by csamuel (✭ supporter ✭, #2624) [Link] VJ said that the only reason that TCP/IP was done in the kernel in Multics in the first place was because that was the only place you could be guaranteed not to get paged out for two minutes at a stretch.
Exokernels Posted Feb 4, 2006 19:44 UTC (Sat) by kbob (guest, #1770) [Link] It would be unfortunate if TCP became incompatible with job control. I often suspend network jobs for various reasons, secure in the knowledge that the kernel will keep the TCP connection alive indefinitely.
Exokernels Posted Feb 5, 2006 1:47 UTC (Sun) by lutchann (subscriber, #8872) [Link] On the other hand, most connection-oriented application protocols these days have a timeout mechanism above the TCP. If you suspend your IMAP or XMPP client for more than a minute or two you're likely to have a broken connection when you foreground the application again.
|
|||||||||||||