From: David Miller <davem@davemloft.net>
To: cl@linux.com
Cc: dlstevens@us.ibm.com, netdev@vger.kernel.org,
netdev-owner@vger.kernel.org, nhorman@tuxdriver.com,
vladislav.yasevich@hp.com
Subject: Re: PATCH: Multicast: Filter multicast traffic per socket mc_list
Date: Thu, 16 Apr 2009 15:15:37 -0700 (PDT) [thread overview]
Message-ID: <20090416.151537.184847548.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0904161133320.15629@qirst.com>
From: Christoph Lameter <cl@linux.com>
Date: Thu, 16 Apr 2009 11:36:10 -0400 (EDT)
> On Thu, 16 Apr 2009, David Stevens wrote:
>
>> This isn't what I suggested-- you have the default backwards. It must
>> default
>> to current behavior, or it's pointless.
>
> If it would default to the current behavior then it would be incompatible
> with the behavior of other operating systems and the surprising behavior
> of the Linux multicast stack would continue to exist. The unusual behavior
> needs to be switched on if wanted for legacy or other reasons.
Umm, no.
We don't break existing applications "by default".
You're being entirely selfish here, you want your application to work
without having to specify the socket option to get the new behavior.
Well guess what? Under Linux you will have to!
next prev parent reply other threads:[~2009-04-16 22:15 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 [this message]
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
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=20090416.151537.184847548.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cl@linux.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev-owner@vger.kernel.org \
--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).