On Sat, May 08, 2010 at 03:55:48PM +0800, Xin, Xiaohui wrote:
Michael,
Sorry, somehow I missed this mail. :-(
Here, we have ever considered 2 ways to utilize the page constructor
API to dispense the user buffers.
One: Modify __alloc_skb() function a bit, it can only allocate a
Michael,
Sorry, somehow I missed this mail. :-(
Here, we have ever considered 2 ways to utilize the page constructor
API to dispense the user buffers.
One: Modify __alloc_skb() function a bit, it can only allocate a
structure of sk_buff, and the data pointer is pointing to a
The idea is simple, just to pin the guest VM user space and then let
host NIC driver has the chance to directly DMA to it.
Isn't it much easier to map the RX ring of the network device into the
guest's address space, have DMA map calls translate guest addresses to
physical/DMA addresses
We provide an zero-copy method which driver side may get external
buffers to DMA. Here external means driver don't use kernel space
to allocate skb buffers. Currently the external buffer can be from
guest virtio-net driver.
The idea is simple, just to pin the guest VM user space and then
let host
From: xiaohui@intel.com
Date: Sun, 25 Apr 2010 17:20:06 +0800
The idea is simple, just to pin the guest VM user space and then let
host NIC driver has the chance to directly DMA to it.
Isn't it much easier to map the RX ring of the network device into the
guest's address space, have DMA
On Sun, Apr 25, 2010 at 02:55:29AM -0700, David Miller wrote:
From: xiaohui@intel.com
Date: Sun, 25 Apr 2010 17:20:06 +0800
The idea is simple, just to pin the guest VM user space and then let
host NIC driver has the chance to directly DMA to it.
Isn't it much easier to map the RX
On Sun, Apr 25, 2010 at 05:20:06PM +0800, xiaohui@intel.com wrote:
We provide an zero-copy method which driver side may get external
buffers to DMA. Here external means driver don't use kernel space
to allocate skb buffers. Currently the external buffer can be from
guest virtio-net driver.
