From: Alex Williamson <alex.williamson@hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: markmc@redhat.com, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-net: Remove RX_EXTRA feature
Date: Tue, 16 Jun 2009 08:29:46 -0600 [thread overview]
Message-ID: <1245162586.20622.9.camel@lappy> (raw)
In-Reply-To: <200906161249.25971.rusty@rustcorp.com.au>
On Tue, 2009-06-16 at 12:49 +0930, Rusty Russell wrote:
> On Tue, 16 Jun 2009 12:15:44 am Alex Williamson wrote:
> > On Mon, 2009-06-15 at 14:48 +0930, Rusty Russell wrote:
> > > It's hard to see
> > > the use case where this feature offers significant advantages over
> > > promisc. Without that, I'd wait until someone reports a need.
> >
> > Thanks for clarifying, a need has been reported. DMX is a proprietary
> > OS that intends to run on KVM and make use of virtio-net. They would
> > like to be able to toggle unicast and multicast independently as well as
> > mask broadcast traffic. The original series re-arranged some of the
> > filter code in the virtio-net backend that allows these filter options
> > to drop out nicely.
>
> That's sufficient for me.
Great, this feature bit removal patch is official dead then.
> Could you re-send feature-based patches if you're happy?
The feature based version already went into the tree via Mark's patch
queue, but I'll bounce you copies in case you have any comments that we
can fixup in tree before we sync the Linux virtio-net header. Thanks,
Alex
prev parent reply other threads:[~2009-06-16 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 19:17 [Qemu-devel] [PATCH] virtio-net: Remove RX_EXTRA feature Alex Williamson
2009-06-14 9:39 ` Michael S. Tsirkin
2009-06-14 13:31 ` Alex Williamson
2009-06-15 5:18 ` Rusty Russell
2009-06-15 14:45 ` Alex Williamson
2009-06-16 3:19 ` Rusty Russell
2009-06-16 14:29 ` Alex Williamson [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=1245162586.20622.9.camel@lappy \
--to=alex.williamson@hp.com \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).