Re: [PATCH 2 of 4] Introduce i386 fibril scheduling

Ingo Molnar <[email protected]> writes:

> and for one of the most important IO 
> disciplines, networking, that is reality already.

Not 100% -- a few things in TCP/IP at least are blocking still.
Mostly relatively obscure things though.

Also the sockets model is currently incompatible with direct zero-copy RX/TX, 
which needs fixing.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Zach Brown <[email protected]>
  • [PATCH 2 of 4] Introduce i386 fibril scheduling
    • From: Zach Brown <[email protected]>
  • Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
    • From: Ingo Molnar <[email protected]>
  • Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
• Next by Date: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
• Previous by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
• Next by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]