From: Stefan Hajnoczi <stefanha@gmail.com>
To: Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU RX offload issues with net device frontend that does not support virtio extensions
Date: Thu, 8 Mar 2012 10:10:15 +0000 [thread overview]
Message-ID: <CAJSP0QXP0SR88-espd7GJt5ROCP2fbpFhNm=kra4PZLXo-VYJg@mail.gmail.com> (raw)
In-Reply-To: <CAOMtban3iL3XOF8zO2Uphi7w9trD2iC5=a6fX4pxnnyS7mpk0A@mail.gmail.com>
On Wed, Mar 7, 2012 at 4:32 PM, Dmitry Fleytman
<dmitry.fleytman@ravellosystems.com> wrote:
> It looks like there is a problem in QEMU related to usage of frontends
> without virtio extensions.
>
> Normally on RX path QEMU receives packet metadata with offloads
> information in virtio header.
Have you tried -netdev tap,vnet_hdr=off ?
I guess the tricky thing is negotiating whether or not to enable the
host IFF_VNET_HDR flag. (Especially with the QEMU "vlan" feature
where the tap isn't peered directly with another device.)
Stefan
prev parent reply other threads:[~2012-03-08 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 16:32 [Qemu-devel] QEMU RX offload issues with net device frontend that does not support virtio extensions Dmitry Fleytman
2012-03-08 10:10 ` 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='CAJSP0QXP0SR88-espd7GJt5ROCP2fbpFhNm=kra4PZLXo-VYJg@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=dmitry.fleytman@ravellosystems.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).