Evgeniy Polyakov wrote: >>> But it looks from this discussion, that it will not prevent from >>> changing in-kernel driver - place a hook into skb allocation path and >>> allocate data from opposing memory - get pages from another side and put >>> them into fragments, then copy headers into skb->data. >>> >>> >> I don't understand this (opposing memory, another side?). Can you >> elaborate? >> > > You want to implement zero-copy network device between host and guest, if > I understood this thread correctly? > So, for sending part, device allocates pages from receiver's memory (or > from shared memory), receiver gets an 'interrupt' and got pages from own > memory, which are attached to new skb and transferred up to the network > stack. > It can be extended to use shared ring of pages. >
This is what Xen does. It is actually less performant than copying, IIRC. The problem with flipping pages around is that physical addresses are cached both in the kvm mmu and in the on-chip tlbs, necessitating expensive page table walks and tlb invalidation IPIs. Note that for sending from the guest an external host can be done copylessly, and for the receive side using a dma engine (like I/OAT) can reduce the cost of the copy. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
