From: Stephen Hemminger <shemminger@linux-foundation•org>
To: David Lamparter <equinox@diac24•net>
Cc: "Nick Carter" <ncarter100@gmail•com>,
netdev@vger•kernel.org, "Michał Mirosław" <mirqus@gmail•com>,
davem@davemloft•net
Subject: Re: [PATCH] bridge: mask forwarding of IEEE 802 local multicast groups
Date: Thu, 28 Jul 2011 08:41:06 -0700 [thread overview]
Message-ID: <20110728084106.22166324@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <20110727111714.GA2027462@jupiter.n2.diac24.net>
On Wed, 27 Jul 2011 13:17:15 +0200
David Lamparter <equinox@diac24•net> wrote:
> On Fri, Jul 15, 2011 at 06:33:45PM +0200, David Lamparter wrote:
> > On Fri, Jul 15, 2011 at 06:03:57PM +0200, David Lamparter wrote:
> > > On Fri, Jul 15, 2011 at 04:44:50PM +0100, Nick Carter wrote:
> > > > On 12 July 2011 12:36, David Lamparter <equinox@diac24•net> wrote:
> > > > > On Mon, Jul 11, 2011 at 08:27:55AM -0700, Stephen Hemminger wrote:
> > > > >> I am still undecided on this. Understand the need, but don't like idea
> > > > >> of bridge behaving in non-conforming manner. Will see if IEEE 802 committee
> > > > >> has any input.
> > > > >
> > > > > The patch doesn't make the bridge behave nonconformant. The default mask
> > > > > is 0, which just keeps the old behaviour.
> >
> > P.S.: I'd like to once more stress this. In my opinion the patch should
> > be merged because it provides desireable functionality at a small cost
> > (one test, one knob) and __does not change any default behaviour__.
>
> Stephen, anything new on this?
No.
Don't like adding yet another hack user visible API which will have
to be maintained for too long. But on the other hand I don't have
a better solution at my finger tips. If better idea doesn't come
along, then we can go with yours.
next prev parent reply other threads:[~2011-07-28 15:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 21:21 [PATCH] bridge: mask forwarding of IEEE 802 local multicast groups Nick Carter
2011-07-01 22:37 ` David Lamparter
2011-07-03 18:30 ` Nick Carter
2011-07-10 16:04 ` Nick Carter
2011-07-11 15:27 ` Stephen Hemminger
2011-07-12 11:36 ` David Lamparter
2011-07-15 15:44 ` Nick Carter
2011-07-15 16:03 ` David Lamparter
2011-07-15 16:33 ` David Lamparter
2011-07-27 11:17 ` David Lamparter
2011-07-28 15:41 ` Stephen Hemminger [this message]
2011-08-15 16:27 ` Nick Carter
2011-08-15 18:25 ` Stephen Hemminger
2011-08-31 20:41 ` Nick Carter
2011-08-31 20:49 ` Stephen Hemminger
2011-08-31 22:00 ` Ed Swierk
2011-09-01 0:16 ` David Lamparter
2011-09-13 19:29 ` Benjamin Poirier
[not found] <CAF5U64C+WgQhfJL3zfVnvzE7p=G61humQCObHGUxAvY2-MGAFQ@mail.gmail.com>
2011-08-12 22:37 ` Ed Swierk
2011-08-12 22:45 ` Stephen Hemminger
2011-08-13 5:43 ` Ed Swierk
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=20110728084106.22166324@nehalam.ftrdhcpuser.net \
--to=shemminger@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=equinox@diac24$(echo .)net \
--cc=mirqus@gmail$(echo .)com \
--cc=ncarter100@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/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