Wei Liu 43e9d19432 xen-netback: remove page tracking facility ... The data flow from DomU to DomU on the same host in current copying scheme with tracking facility: copy DomU --------> Dom0 DomU | ^ |____________________________| copy The page in Dom0 is a page with valid MFN. So we can always copy from page Dom0, thus removing the need for a tracking facility. copy copy DomU --------> Dom0 -------> DomU Simple iperf test shows no performance regression (obviously we copy twice either way): W/ tracking: ~5.3Gb/s W/o tracking: ~5.4Gb/s Signed-off-by: Wei Liu <wei.liu2@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Matt Wilson <msw@amazon.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2013-08-29 01:18:04 -04:00
..
common.h	xen-netback: split event channels support for Xen backend driver	2013-05-23 18:40:37 -07:00
interface.c	xen-netback: split event channels support for Xen backend driver	2013-05-23 18:40:37 -07:00
Makefile
netback.c	xen-netback: remove page tracking facility	2013-08-29 01:18:04 -04:00
xenbus.c	xen-netback: xenbus.c: use more current logging styles	2013-07-02 00:52:55 -07:00