From: Stephen Hemminger <stephen@networkplumber•org>
To: vyasevic@redhat•com
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"bridge@lists•linux-foundation.org"
<bridge@lists•linux-foundation.org>,
"Oleg A. Arkhangelsky" <sysoleg@yandex•ru>
Subject: Re: [PATCH net-next 0/4] Allow bridge to function in non-promisc mode
Date: Wed, 13 Mar 2013 08:39:32 -0700 [thread overview]
Message-ID: <20130313083932.6483876f@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <51406D2D.30703@redhat.com>
On Wed, 13 Mar 2013 08:12:29 -0400
Vlad Yasevich <vyasevic@redhat•com> wrote:
> On 03/13/2013 02:22 AM, "Oleg A. Arkhangelsky" wrote:
> >
> >
> > 13.03.2013, 05:45, "Vlad Yasevich" <vyasevic@redhat•com>:
> >
> >> The series adds an ability for the bridge to function in non-promiscuous mode.
> >
> > What is the practical applications for such setup? In other words,
> > in which cases I would want to put bridge into non-promiscuous
> > mode and specify some uplink ports?
> >
>
> On of the applications would be when bridge is an edge device servicing
> a VM deployment. Each of the VMs knows the mac address that the guest
> has and may program that mac onto the uplinks.
Why wouldn't that environment just use macvlan?
Is it because changing libvirt is harder than changing the kernel?
next prev parent reply other threads:[~2013-03-13 15:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 1:45 [PATCH net-next 0/4] Allow bridge to function in non-promisc mode Vlad Yasevich
2013-03-13 1:45 ` [PATCH net-next 1/4] bridge: Add sysfs interface to control promisc mode Vlad Yasevich
2013-03-13 15:38 ` Stephen Hemminger
2013-03-13 15:44 ` Vlad Yasevich
2013-03-13 1:45 ` [PATCH net-next 2/4] bridge: Allow an ability to designate an uplink port Vlad Yasevich
2013-03-13 20:33 ` Michael S. Tsirkin
2013-03-13 22:54 ` Stephen Hemminger
2013-03-13 23:43 ` Vlad Yasevich
2013-03-14 14:53 ` Dan Williams
2013-03-13 1:45 ` [PATCH net-next 3/4] bridge: Implement IFF_UNICAST_FLT Vlad Yasevich
2013-03-13 1:45 ` [PATCH net-next 4/4] bridge: sync device list when a new uplink is designated Vlad Yasevich
2013-03-13 6:22 ` [PATCH net-next 0/4] Allow bridge to function in non-promisc mode "Oleg A. Arkhangelsky"
2013-03-13 12:12 ` Vlad Yasevich
2013-03-13 15:39 ` Stephen Hemminger [this message]
2013-03-13 15:45 ` Vlad Yasevich
2013-03-13 16:09 ` Stephen Hemminger
2013-03-13 17:04 ` Vlad Yasevich
2013-03-13 18:56 ` [Bridge] " Joel Wirāmu Pauling
2013-03-13 20:08 ` Michael S. Tsirkin
2013-03-13 20:31 ` Michael S. Tsirkin
2013-03-14 15:10 ` Vlad Yasevich
2013-03-14 17:46 ` 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=20130313083932.6483876f@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber$(echo .)org \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sysoleg@yandex$(echo .)ru \
--cc=vyasevic@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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