qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU RX offload issues with net device frontend that does not support virtio extensions
Date: Wed, 7 Mar 2012 18:32:43 +0200	[thread overview]
Message-ID: <CAOMtban3iL3XOF8zO2Uphi7w9trD2iC5=a6fX4pxnnyS7mpk0A@mail.gmail.com> (raw)

Hello,

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.
In particular there is an information about checksumming state. For
example, when
packet is being transferred from guest to guest with offloads enabled
on transmitter side,
checksums won't be calculated, special flag will be set instead in
virtio header indicating that the checksum is ok.
Based on this flag device may notify guest that checksum verification
for this packet is not required.

Now, when virtio header is not supported on receiver side, there is no
way device may be notified about the checksum state.
Packet will be indicated to the guest as is and will be dropped by
guest's network stack.

I've tested this scenario with virtio devices and observed the issue described.

Do I miss something? Is there any configuration option or something
I'm not aware about?

Thanks in advance,
Dmitry Fleytman.

             reply	other threads:[~2012-03-07 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 16:32 Dmitry Fleytman [this message]
2012-03-08 10:10 ` [Qemu-devel] QEMU RX offload issues with net device frontend that does not support virtio extensions Stefan Hajnoczi

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='CAOMtban3iL3XOF8zO2Uphi7w9trD2iC5=a6fX4pxnnyS7mpk0A@mail.gmail.com' \
    --to=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).