From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luigi Rizzo <rizzo@iet.unipi.it>
Cc: Giuseppe Lettieri <g.lettieri@iet.unipi.it>,
qemu-devel <qemu-devel@nongnu.org>,
Vincenzo Maffione <v.maffione@gmail.com>
Subject: Re: [Qemu-devel] difference between receive_raw() and receive() NetClientInfo methods ?
Date: Fri, 7 Jun 2013 14:29:12 +0200 [thread overview]
Message-ID: <20130607122912.GB11350@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CA+hQ2+jHh84ygXR48w-t+b41N3bODzHRkOE2WbSPgGURYJwVzA@mail.gmail.com>
On Thu, Jun 06, 2013 at 11:40:37AM +0200, Luigi Rizzo wrote:
> Can someone clarify what is the difference between the two methods
> r
> eceive_raw() and receive() in NetClientInfo ?
receive_raw() builds an empty vnet header, if necessary. It is used to
send a gratuitous ARP reply from inside QEMU.
In the case where the NIC and its peer use vnet headers, packets
generated by QEMU internally cannot use ->receive() since they don't
know how to use the vnet header. ->receive_raw() takes care of that.
Stefan
prev parent reply other threads:[~2013-06-07 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:40 [Qemu-devel] difference between receive_raw() and receive() NetClientInfo methods ? Luigi Rizzo
2013-06-07 12:29 ` Stefan Hajnoczi [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=20130607122912.GB11350@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=g.lettieri@iet.unipi.it \
--cc=qemu-devel@nongnu.org \
--cc=rizzo@iet.unipi.it \
--cc=v.maffione@gmail.com \
/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).