qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: Stefan Fritsch <sf@sfritsch.de>
Cc: vyasevic@redhat.com, qemu-devel@nongnu.org,
	Anthony Liguori <aliguori@amazon.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-net: Do not filter VLANs without F_CTRL_VLAN
Date: Tue, 25 Mar 2014 17:39:12 +0800	[thread overview]
Message-ID: <20140325093912.GA2071@amosk.info> (raw)
In-Reply-To: <1907885.BLXM6R4UH8@k>

On Wed, Mar 19, 2014 at 11:38:57PM +0100, Stefan Fritsch wrote:
> Hi,
> 
> Am Dienstag, 25. Februar 2014, 11:06:33 schrieb Amos Kong:
> > > > On Wed, Feb 12, 2014 at 10:46:28PM +0100, Stefan Fritsch wrote:
> > > > > If VIRTIO_NET_F_CTRL_VLAN is not negotiated, do not filter out
> > > > > all
> > > > > VLAN-tagged packets but send them to the guest.
> 
> 
> AFAICS, no fix has been committed, yet. Is there anything I need to do 
> to get this fixed?
 
Michael asked in IRC to continually add a RxState for vlan in
RxFilter notification through QMP events.

(sorry I didn't talk too much becaused I'm in meeting)

I mentioned in [1] [2], we don't need to add this new state
if we apply patch Stefan's patch[3]

Michael said Stefan's fix is wrong, but the problem exists.
The problem is the bug fixed by [3], not the problem that was
mentioned in [4] 


Michael, what's wrong with Stefan's patch?


Thanks, Amos

[1] http://lists.gnu.org/archive/html/qemu-devel/2014-02/msg03835.html
[2] https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg04434.html
[3] virtio-net: Do not filter VLANs without F_CTRL_VLAN
[4] https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg02604.html


> > > > Can we just update receive_filter() to filter out VLAN-tagged
> > > > packets only when VIRTIO_NET_F_CTRL_VLAN is negotiated?
> > 
> > If we change receive_filter(), we also need a flag to indicate
> > management this feature isn't negotiated, management will do some
> > additional operation to host device to get same effect.
> >  
> > 
> > > We could. But this adds a (very small) per-packet overhead while
> > > my patch  only adds overhead during reset. Therefore I didn't
> > > take that approach. But if changing receive_filter() makes
> > > management much easier, that could be acceptable.
> > 
> > Actually your solution is better, QEMU will return a long list
> > [0,1,2,...4095] to management, host device will filter all the vlan
> > packets and send to QEMU.
> > 
> > So the problem raised by mst doesn't exist.
> 
> Cheers,
> Stefan
> 

-- 
			Amos.

  reply	other threads:[~2014-03-25  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 21:06 [Qemu-devel] virtio-net VLAN filtering bug Stefan Fritsch
2014-02-12 21:46 ` [Qemu-devel] [PATCH] virtio-net: Do not filter VLANs without F_CTRL_VLAN Stefan Fritsch
2014-02-16 10:33   ` Michael S. Tsirkin
2014-02-17 14:57     ` Eric Blake
2014-02-17 21:31     ` Stefan Fritsch
2014-02-21  9:58   ` Amos Kong
2014-02-23  8:27     ` Stefan Fritsch
2014-02-25  3:06       ` Amos Kong
2014-03-19 22:38         ` Stefan Fritsch
2014-03-25  9:39           ` Amos Kong [this message]
2014-03-25 10:08             ` Michael S. Tsirkin

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=20140325093912.GA2071@amosk.info \
    --to=akong@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sf@sfritsch.de \
    --cc=vyasevic@redhat.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).