On 4/19/08, Anthony Liguori [EMAIL PROTECTED] wrote:
Blue Swirl wrote:
On 4/17/08, Anthony Liguori [EMAIL PROTECTED] wrote:
Yes, the vector version of packet receive is tough. I'll take a look
at
your patch. Basically, you need to associate a set of RX vectors with
each
On 4/17/08, Anthony Liguori [EMAIL PROTECTED] wrote:
Yes, the vector version of packet receive is tough. I'll take a look at
your patch. Basically, you need to associate a set of RX vectors with each
VLANClientState and then when it comes time to deliver a packet to the VLAN,
before calling
Blue Swirl wrote:
On 4/17/08, Anthony Liguori [EMAIL PROTECTED] wrote:
Yes, the vector version of packet receive is tough. I'll take a look at
your patch. Basically, you need to associate a set of RX vectors with each
VLANClientState and then when it comes time to deliver a packet to
On 4/16/08, Anthony Liguori [EMAIL PROTECTED] wrote:
Blue Swirl wrote:
On 4/16/08, Anthony Liguori [EMAIL PROTECTED] wrote:
This patch introduces a DMA API and plumbs support through the DMA
layer. We
use a mostly opaque structure, IOVector to represent a scatter/gather
list of
Blue Swirl wrote:
I fixed the bug, now pcnet works. Performance is improved by a few
percent. The problem was that the vector was not freed. Maybe dynamic
allocation is a bit fragile. In this case, the length of the vector is
known, so it could be allocated once at init time. But would this
On 4/16/08, Anthony Liguori [EMAIL PROTECTED] wrote:
This patch introduces a DMA API and plumbs support through the DMA layer. We
use a mostly opaque structure, IOVector to represent a scatter/gather list of
physical memory. Associated with each IOVector is a read/write function and
an
Blue Swirl wrote:
On 4/16/08, Anthony Liguori [EMAIL PROTECTED] wrote:
This patch introduces a DMA API and plumbs support through the DMA layer. We
use a mostly opaque structure, IOVector to represent a scatter/gather list
of
physical memory. Associated with each IOVector is a
