public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: david@lang.hm
Cc: linux-kernel@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: When does Linux drop UDP packets?
Date: Thu, 25 Jun 2009 08:38:05 +0100	[thread overview]
Message-ID: <20090625073805.GB2014@woodchuck> (raw)
In-Reply-To: <20090625061348.GA31407@gondor.apana.org.au>

Hi,

* Herbert Xu <herbert@gondor.apana.org.au> [2009-06-25 14:13:48+0800]:
> 
> On Wed, Jun 24, 2009 at 10:37:14PM -0700, david@lang.hm wrote:
> >
> > please explain more? how do they differ?
> 
> An IGMP-snooping switch will only forward multicast traffic to
> ports that have subscribed to that group.  Broadcast traffic
> on the otherhand is forwarded to all ports.
>
[directing over to David...]

The more intelligent switches actually peek at L3/L4 (even if it's just 
a L2 switch, like a Cisco 2950) to decode IGMP packets as they come out 
from the hosts.  The switch uses that to build up an Ethernet multicast 
routing table, in addition to it's usual unicast based one.

If you bought a managed switch in the past five years (ours from 8 years 
ago that we have just binned also supported it) it should support 
IGMP snooping.  Any one buying switches now needs to make sure they 
support IPv6 and MLD snooping...bearing in mind you are going to be 
lumbered with those switches for at least five years.

In addition and mentioned before, the NIC in hardware will also filter 
any multicast traffic that is un-needed if you are using el-cheapo 
switches; crime and punishment.  Broadcast traffic *always* spans the 
whole VLAN and *always* gets passed up to the OS to make decisions on 
whether to process the packet or not.

Now, when you roll back in the 'automaticness' of service discovery and 
other such things on the network...multicast is a very powerful tool.  
Just because it can be many<->many or one<->many does not mean it cannot 
be just as efficiently used to bootstrap one<->one communications.

Cheers

-- 
Alexander Clouter
.sigmonster says: Don't take life seriously, you'll never get out alive.

      reply	other threads:[~2009-06-25  7:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 14:53 When does Linux drop UDP packets? Philipp Reh
2009-06-04 15:57 ` Steven Rostedt
     [not found]   ` <20090604161015.GA17303@miyuki>
     [not found]     ` <alpine.DEB.2.00.0906041222450.14994@gandalf.stny.rr.com>
2009-06-04 16:34       ` Steven Rostedt
2009-06-04 16:57         ` Steven Rostedt
2009-06-04 17:46         ` Jaswinder Singh Rajput
2009-06-04 21:07           ` Steven Rostedt
2009-06-04 17:57   ` david
2009-06-04 18:44     ` Eric Dumazet
2009-06-04 18:49       ` david
2009-06-11 23:40   ` Nifty niftylinkern Mitch
2009-06-04 22:03 ` Alexander Clouter
2009-06-04 23:19   ` david
2009-06-05 19:10     ` Alexander Clouter
2009-06-05 19:15       ` david
2009-06-05 19:29         ` Alexander Clouter
2009-06-24  7:47     ` Herbert Xu
2009-06-25  4:32       ` david
2009-06-25  5:00         ` Herbert Xu
2009-06-25  5:37           ` david
2009-06-25  6:13             ` Herbert Xu
2009-06-25  7:38               ` Alexander Clouter [this message]

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=20090625073805.GB2014@woodchuck \
    --to=alex@digriz.org.uk \
    --cc=david@lang.hm \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox