From: Nivedita Singhvi <niv@us.ibm.com>
To: Christoph Lameter <cl@linux.com>
Cc: David Miller <davem@davemloft.net>,
nhorman@tuxdriver.com, netdev@vger.kernel.org,
vladislav.yasevich@hp.com, dlstevens@us.ibm.com
Subject: Re: PATCH: Multicast: Filter multicast traffic per socket mc_list
Date: Fri, 17 Apr 2009 08:37:36 -0700 [thread overview]
Message-ID: <49E8A240.8050404@us.ibm.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0904170952050.11877@qirst.com>
Christoph Lameter wrote:
> On Thu, 16 Apr 2009, David Miller wrote:
>
>> No Christoph, do this right.
>>
> > Linux by default will behave the way it has for 15+ years. And if an
>> application wants new behavior, you have to ask for it.
>>
>> End of story.
>
> This is not right. All other OSes filter multicast traffic according to
> the multicast groups subscribed too (and that includes the evil one).
> There is no requirement of asking for "new" behavior. Why should multicast
> applications have to add special code to request something that comes by
> default on other platforms?
I need the current behaviour to not change, as it would
break some people I support. DaveM is making the right
decision here, and I fully support this.
And I'm one of those people working on low latency and
hoping messaging clients get better in their multicast
usage..just that this is not one of those ways.
Ideally, you could tweak OS environment configuration
setting, if you don't want per socket. But it cannot
be the default.
thanks,
Nivedita
next prev parent reply other threads:[~2009-04-17 15:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 14:38 PATCH: Multicast: Filter multicast traffic per socket mc_list Christoph Lameter
2009-04-16 15:09 ` David Stevens
2009-04-16 15:36 ` Christoph Lameter
2009-04-16 22:15 ` David Miller
2009-04-16 15:15 ` Neil Horman
2009-04-16 15:36 ` Christoph Lameter
2009-04-16 17:44 ` Neil Horman
2009-04-16 19:12 ` Christoph Lameter
2009-04-16 20:56 ` David Stevens
2009-04-16 21:04 ` Christoph Lameter
2009-04-16 21:54 ` David Stevens
2009-04-16 22:19 ` David Miller
2009-04-16 21:19 ` Vlad Yasevich
2009-04-16 22:20 ` David Miller
2009-04-16 22:22 ` David Stevens
2009-04-16 23:30 ` Stephen Hemminger
2009-04-17 0:01 ` Vlad Yasevich
2009-04-16 22:16 ` David Miller
2009-04-17 13:56 ` Christoph Lameter
2009-04-17 15:37 ` Nivedita Singhvi [this message]
2009-04-17 16:02 ` Christoph Lameter
2009-04-17 16:28 ` Nivedita Singhvi
2009-04-17 22:24 ` David Miller
2009-04-20 18:10 ` Christoph Lameter
2009-04-17 21:31 ` David Stevens
2009-04-20 16:43 ` Christoph Lameter
2009-04-20 18:46 ` David Stevens
2009-04-16 15:24 ` Vlad Yasevich
2009-04-16 15:39 ` Christoph Lameter
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=49E8A240.8050404@us.ibm.com \
--to=niv@us.ibm.com \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vladislav.yasevich@hp.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).