From: Steve Chen <schen@mvista.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
mhuth@mvista.com, netdev@vger.kernel.org,
netdev-owner@vger.kernel.org
Subject: Re: [Fwd: Re: [PATCH] Multicast packet reassembly can fail]
Date: Wed, 28 Oct 2009 16:11:08 -0500 [thread overview]
Message-ID: <1256764269.3153.494.camel@linux-1lbu> (raw)
In-Reply-To: <OFF3C0AE1C.0C392C88-ON8825765D.006F8D81-8825765D.006FF4C0@us.ibm.com>
On Wed, 2009-10-28 at 13:22 -0700, David Stevens wrote:
> netdev-owner@vger.kernel.org wrote on 10/28/2009 11:25:39 AM:
>
> > I see the point you are making. I assumed, probably incorrectly, that
> > since eth0 and eth1 have different IP address. I would get a complete
> > series of fragments for each interface. Perhaps, I should really be
> > looking up the stack to see why packets were dropped. Please correct me
> > if I'm mistaken. The normal behavior is that application should be
> > receiving either 2 (scenario 1) or 1 (scenario 2) packets.
>
> Steve,
> If you didn't join the group on both interfaces, you won't receive
> two copies in the first place; the unjoined NIC won't deliver anything
> up the stack that isn't in it's multicast address filter.
>
> +-DLS
Thanks for the inputs. I'll revisit the issue.
Steve
prev parent reply other threads:[~2009-10-28 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1256740748.3153.418.camel@linux-1lbu>
[not found] ` <4AE86420.3040607@gmail.com>
2009-10-28 17:05 ` [Fwd: Re: [PATCH] Multicast packet reassembly can fail] Steve Chen
2009-10-28 17:26 ` Eric Dumazet
2009-10-28 18:25 ` Steve Chen
2009-10-28 20:22 ` David Stevens
2009-10-28 21:11 ` Steve Chen [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=1256764269.3153.494.camel@linux-1lbu \
--to=schen@mvista.com \
--cc=dlstevens@us.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=mhuth@mvista.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.