From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Alex Williamson <alex.williamson@hp.com>
Subject: Re: [Qemu-devel] Re: [PATCH 6/7] virtio-net: Add new RX filter controls
Date: Wed, 10 Jun 2009 12:35:27 +0300 [thread overview]
Message-ID: <20090610093527.GC6844@redhat.com> (raw)
In-Reply-To: <20090610092235.GF15949@redhat.com>
On Wed, Jun 10, 2009 at 12:22:35PM +0300, Gleb Natapov wrote:
> On Wed, Jun 10, 2009 at 12:17:55PM +0300, Michael S. Tsirkin wrote:
> > On Wed, Jun 10, 2009 at 12:13:21PM +0300, Gleb Natapov wrote:
> > > On Wed, Jun 10, 2009 at 12:07:59PM +0300, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 10, 2009 at 10:58:44AM +0200, Jan Kiszka wrote:
> > > > > Michael S. Tsirkin wrote:
> > > > > > On Tue, Jun 09, 2009 at 05:42:32PM +0200, Jan Kiszka wrote:
> > > > > >> The same is true for PF_PACKET (or does libpcap actually use that
> > > > > >> internally?). Haven't analyzed the reasons in details yet, but I bet
> > > > > >> it's not solvable in user space.
> > > > > >>
> > > > > >> Jan
> > > > > >
> > > > > > I think you can load the veth module, and attach veth to a bridge.
> > > > >
> > > > > Sorry, my brain is not yet working at full speed: What do we gain for
> > > > > the initial problem that we want to bridge to an existing network device
> > > > > without having to move management tools like dhcpcd to the corresponding
> > > > > brX?
> > > > >
> > > > > Jan
> > > >
> > > > Nothing :). I was only saying that IIUC the problem is not with
> > > > PF_PACKET itself - I think that PF_PACKET + veth can be used
> > > > as a replacement for tap.
> > > >
> > > And the point is...?
> >
> > tap requires bridging, PF_PACKET can attach to a physical device.
> >
> Why tap requires bridging? User requires bridging, so he uses bridge.
Yea, good point :)
> Look above, you wrote "I think you can load the veth module, and attach
> veth to a bridge."
--
MST
next prev parent reply other threads:[~2009-06-10 9:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 20:46 [Qemu-devel] [PATCH 0/7] virtio-net: Filter cleanup/improvements Alex Williamson
2009-06-05 20:46 ` [Qemu-devel] [PATCH 1/7] virtio-net: Add version_id 7 placeholder for vnet header support Alex Williamson
2009-06-05 20:46 ` [Qemu-devel] [PATCH 2/7] virtio-net: Use a byte to store RX mode flags Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 3/7] virtio-net: reorganize receive_filter() Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 4/7] virtio-net: Fix MAC filter overflow handling Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 5/7] virtio-net: MAC filter optimization Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 6/7] virtio-net: Add new RX filter controls Alex Williamson
2009-06-06 20:48 ` Michael S. Tsirkin
2009-06-08 19:01 ` Alex Williamson
2009-06-08 19:18 ` Anthony Liguori
2009-06-08 19:29 ` Daniel P. Berrange
2009-06-08 21:03 ` Anthony Liguori
2009-06-09 9:57 ` Daniel P. Berrange
2009-06-09 15:00 ` Jamie Lokier
2009-06-09 15:42 ` [Qemu-devel] " Jan Kiszka
2009-06-09 23:50 ` Jamie Lokier
2009-06-10 8:46 ` Michael S. Tsirkin
2009-06-10 8:58 ` Jan Kiszka
2009-06-10 9:07 ` Michael S. Tsirkin
2009-06-10 9:13 ` Gleb Natapov
2009-06-10 9:17 ` Michael S. Tsirkin
2009-06-10 9:22 ` Gleb Natapov
2009-06-10 9:35 ` Michael S. Tsirkin [this message]
2009-06-08 20:18 ` [Qemu-devel] " Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 7/7] virtio-net: Increase filter and control limits Alex Williamson
2009-06-06 20:44 ` Michael S. Tsirkin
2009-06-08 18:49 ` Alex Williamson
2009-06-09 19:25 ` [Qemu-devel] [PATCH 0/7] virtio-net: Filter cleanup/improvements Mark McLoughlin
2009-06-09 21:08 ` Alex Williamson
2009-06-10 6:51 ` Rusty Russell
2009-06-10 20:43 ` Alex Williamson
2009-06-12 17:07 ` Mark McLoughlin
2009-06-12 19:19 ` Alex Williamson
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=20090610093527.GC6844@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@hp.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.