Messages in this thread |  | | Date | Sun, 3 Sep 2000 16:20:22 +0200 | From | almesber@lrc ... | Subject | Re: zero-copy TCP |
| |
Ingo Molnar wrote: > On 2 Sep 2000, Jes Sorensen wrote: > > Besides that you need to do copy-on-write if you want to be able to do > > zero copy on write() from user space [...] > > i agree that this is hard - i'm not sure wether we want to go the pain to > enable anonymous-buffer write()s do zero-copy.
If we go for a Linux-specific solution anyway, maybe one could add another send{,to,msg} flag that makes send*(2)'s buffer access non-atomic. That way, the kernel only needs to make sure the pages don't disappear, but there's no need for expensive MMU games.
Of course, this would give applications a way for generating packets with an incorrect TCP/UDP checksum, so maybe that should be protected by a capability then, maybe CAP_NET_RAW.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |