From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Catalin Vasile <catalinvasile92@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [vhost-net] handle_tx: extract data from vq when !zcopy_used
Date: Fri, 10 Apr 2015 17:14:34 +0200 [thread overview]
Message-ID: <20150410171434.20f0b91f@bahia.local> (raw)
In-Reply-To: <CAOMf8tonLt2sUi-LYBc_Ytp5xkVOHKmX=Z+V5NXY_Yn68KJBDA@mail.gmail.com>
On Fri, 10 Apr 2015 15:58:33 +0300
Catalin Vasile <catalinvasile92@gmail.com> wrote:
> I'm really confused.
> Where does vhost-net (handle_tx) actually extract data from vq when zero
> copy is not used?
> I just see it popping a vq element, but not actually copying anything from
> there.
vhost-net just passes the pointers to the socket, whether zero copy is used
or not:
err = sock->ops->sendmsg(NULL, sock, &msg, len);
BTW, I think virtualization@lists.linux-foundation.org would have been more
appropriate since this isn't a about QEMU.
Cheers.
--
Greg
prev parent reply other threads:[~2015-04-10 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 12:58 [Qemu-devel] [vhost-net] handle_tx: extract data from vq when !zcopy_used Catalin Vasile
2015-04-10 15:14 ` Greg Kurz [this message]
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=20150410171434.20f0b91f@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=catalinvasile92@gmail.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).