netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, netdev@vger.kernel.org
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Tue, 12 Feb 2013 12:43:31 +0200	[thread overview]
Message-ID: <20130212104331.GA23495@redhat.com> (raw)
In-Reply-To: <D40E1487-27E9-40B3-B007-085B432E5600@dlhnet.de>

On Tue, Feb 12, 2013 at 11:11:45AM +0100, Peter Lieven wrote:
> 
> Am 12.02.2013 um 10:54 schrieb "Michael S. Tsirkin" <mst@redhat.com>:
> 
> > On Tue, Feb 12, 2013 at 01:39:07PM +0400, Michael Tokarev wrote:
> >> 12.02.2013 13:10, Peter Lieven wrote:
> >> []
> >> 
> >> Guys, can we please trim the excessive quoting just a bit? ;)
> >> 
> >>>>> If have set this option for 2 weeks now and not seen this problem again.
> >>>>> How does this flag work with the recently added tap multiqueue support?
> >> 
> >>>> This will be the only option in 3.8.
> >> 
> >>> Ok, but wouldn`t it be good to set it in qemu for kernels <3.8?
> >> 
> >> I'd say for kernels without mq support, not for <3.8, right? :)
> >> 
> >> Thanks,
> >> 
> >> /mjt
> > 
> > It's harmless to always set this flag, on 3.8 it does nothing.
> 
> And kernels <3.8 do not have multi queue support?
> 
> Peter

Let's be specific. Multiqueue support in qemu uses TUNSETQUEUE ioctl.
No kernel released by Linus so far has support for this ioctl in tun device,
but it has been merged so should be in 3.8.

> > 
> > -- 
> > MST

  reply	other threads:[~2013-02-12 10:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 14:29 tap devices not receiving packets from a bridge Peter Lieven
2012-11-23  7:02 ` [Qemu-devel] " Stefan Hajnoczi
2012-11-23  9:41   ` Peter Lieven
2012-11-23 11:01     ` Michael S. Tsirkin
2012-11-23 11:02       ` Peter Lieven
2013-01-22  9:04       ` Peter Lieven
2013-01-22  9:43         ` Peter Lieven
2013-01-23 10:03         ` [Qemu-devel] " Michael S. Tsirkin
2013-02-12  7:06           ` Peter Lieven
2013-02-12  9:08             ` [Qemu-devel] " Michael S. Tsirkin
2013-02-12  9:10               ` Peter Lieven
2013-02-12  9:29                 ` Michael S. Tsirkin
2013-02-12  9:39                 ` Michael Tokarev
2013-02-12  9:54                   ` Michael S. Tsirkin
2013-02-12 10:11                     ` [Qemu-devel] " Peter Lieven
2013-02-12 10:43                       ` Michael S. Tsirkin [this message]
2013-05-14 14:21             ` Nicholas Thomas
2013-05-14 14:28               ` Peter Lieven
2013-05-14 14:49                 ` Nicholas Thomas
2013-05-15 11:00                   ` [Qemu-devel] " Nicholas Thomas
2013-05-16  6:24                     ` Michael S. Tsirkin
2013-05-16  6:27                       ` Michael S. Tsirkin
2013-05-16  8:20                         ` Nicholas Thomas
2013-05-16  8:40                           ` Michael S. Tsirkin
2013-05-16  8:47                             ` Peter Lieven
2013-05-16 11:27                             ` Nicholas Thomas
2013-05-16 12:09                               ` Michael S. Tsirkin
2012-11-29 18:58   ` Peter Lieven

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=20130212104331.GA23495@redhat.com \
    --to=mst@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=netdev@vger.kernel.org \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).