From: Eric Dumazet <dada1@cosmosbay.com>
To: Dave Boutcher <daveboutcher@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: IGMP Join dropping multicast packets
Date: Tue, 17 Mar 2009 08:08:23 +0100 [thread overview]
Message-ID: <49BF4C67.9000808@cosmosbay.com> (raw)
In-Reply-To: <49BEA1ED.4010907@cosmosbay.com>
Eric Dumazet a écrit :
> Dave Boutcher a écrit :
>> On Sat, Mar 14, 2009 at 9:37 PM, Eric Dumazet <dada1@cosmosbay.com> wrote:
>>> Dave Boutcher a écrit :
>>>> I'm running into an interesting problem with joining multiple
>>>> multicast feeds. If you join multiple multicast feeds using
>>>> setsockopt(...,IP_ADD_MEMBERSHIP...) it causes packets on UNRELATED
>>>> multicast feeds to get dropped. We have a multicast feed on a rock
>>>> solid network, and we were very surprised to see dropped packets. The
>>>> cause was a different process/program being run by a different user
>>>> joining a bunch of mulitcast feeds.
>>> I could not reproduce the problem on my machines (bnx2 adapter), even if changing
>>> NUMSOCK from 55 to 200 in joiner.c
>> Thanks for trying Eric. Based on your email I did some more testing
>> and thus far I've
>> only recreated this on x86_64 arches, not on i386. Which arch did you
>> try it on?
>
> I tried both, 32 and 64 bit kernels. No problems so far.
>
> Could you post a linux kernel .config of a non 'working' machine, and dmesg output ?
>
Also, is using a third machine to start your joiner program is able to trigger
packet losses too ?
next prev parent reply other threads:[~2009-03-17 7:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 20:16 IGMP Join dropping multicast packets Dave Boutcher
2009-03-15 2:37 ` Eric Dumazet
2009-03-16 2:04 ` Dave Boutcher
2009-03-16 19:01 ` Eric Dumazet
2009-03-17 7:08 ` Eric Dumazet [this message]
2009-03-18 3:50 ` Dave Boutcher
2009-03-18 7:38 ` Eric Dumazet
2009-03-18 17:24 ` Brandeburg, Jesse
2009-03-19 1:48 ` Dave Boutcher
2009-03-19 1:51 ` Dave Boutcher
2009-03-20 20:36 ` Brandeburg, Jesse
2009-03-19 5:46 ` David Miller
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=49BF4C67.9000808@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=daveboutcher@gmail.com \
--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 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).