From: "Blue Swirl" <blauwirbel@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
Marcelo Tosatti <marcelo@kvack.org>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 1/5] PCI DMA API (v3)
Date: Sat, 19 Apr 2008 22:40:29 +0300 [thread overview]
Message-ID: <f43fc5580804191240i4dc7f820s77a36678e30e7dae@mail.gmail.com> (raw)
In-Reply-To: <4807ADA7.7000500@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On 4/17/08, Anthony Liguori <aliguori@us.ibm.com> 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 fd_read, see if there is an RX vector available for the
> client.
>
> In the case of tap, I want to optimize further and do the initial readv()
> to one of the clients RX buffers and then copy that RX buffer to the rest of
> the clients if necessary.
The vector versions should also help SLIRP to add IP and Ethernet
headers to the incoming packets.
I made an initial version of the vectored AIO SCSI with ESP. It does
not work, but I can see that just using the vectors won't give too
much extra performance, because at least initially the vector length
is 1. Collecting the statuses may be tricky.
[-- Attachment #2: block_aio_rw_v.diff --]
[-- Type: plain/text, Size: 10010 bytes --]
next prev parent reply other threads:[~2008-04-19 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 22:11 [Qemu-devel] [PATCH 1/5] PCI DMA API (v3) Anthony Liguori
2008-04-15 22:11 ` [Qemu-devel] [PATCH 2/5] virtio for QEMU (v3) Anthony Liguori
2008-04-15 22:11 ` [Qemu-devel] [PATCH 3/5] virtio network driver (v3) Anthony Liguori
2008-04-15 22:11 ` [Qemu-devel] [PATCH 4/5] virtio block " Anthony Liguori
2008-04-15 22:11 ` [Qemu-devel] [PATCH 5/5] virtio balloon " Anthony Liguori
2008-04-16 19:51 ` [Qemu-devel] [PATCH 1/5] PCI DMA API (v3) Blue Swirl
2008-04-16 19:54 ` Anthony Liguori
2008-04-17 19:27 ` Blue Swirl
2008-04-17 20:05 ` Anthony Liguori
2008-04-19 19:40 ` Blue Swirl [this message]
2008-04-19 20:02 ` [kvm-devel] " Anthony Liguori
2008-04-20 6:42 ` Blue Swirl
2008-04-20 19:29 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580804191240i4dc7f820s77a36678e30e7dae@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).