From: David Miller <davem@davemloft.net>
To: or.gerlitz@gmail.com
Cc: rdreier@cisco.com, cl@linux-foundation.org,
netdev@vger.kernel.org, yosefe@voltaire.com
Subject: Re: IPoIB: Fix multicast packet drops before join is complete
Date: Thu, 11 Jun 2009 04:57:21 -0700 (PDT) [thread overview]
Message-ID: <20090611.045721.05821546.davem@davemloft.net> (raw)
In-Reply-To: <15ddcffd0906110445x25e2b2c5qa8445e0e1b344ef4@mail.gmail.com>
From: Or Gerlitz <or.gerlitz@gmail.com>
Date: Thu, 11 Jun 2009 14:45:28 +0300
> On Wed, Jun 10, 2009 at 3:01 PM, David Miller<davem@davemloft.net> wrote:
>> From: Or Gerlitz <or.gerlitz@gmail.com>
>
>>> for --unicast-- the same problem [...] will come into play under both Ethernet and IB,
>>> so the user is limited by the socket buffer len and the neigh unres_qlen systcl.
>
>> But this generally does not cause problems via ARP, why might that
>> be? Because resolution is 1) rare 2) quick. Both of which do not
>> apply to this IPoIB case.
>
> To be precise, I don't see why ARP resolution is more rare then
> joining to a multicast group on behalf of a sender in IPoIB, they
> both happen on the first and if/when the kernel deletes the
> neighbour.
There are two issues:
1) Ethernet does not have to "resolve" anything for multicast sends.
Therefore this issue is IPoIB specific.
2) ARP's tend to resolve on the DNS request for the site, or the
initial connection attempt. Both of which are single packets,
easily retransmitted, and the dropping of which does not result in
losing significant application data. The multicast case over IPoIB
does drop tons of actual application data.
next prev parent reply other threads:[~2009-06-11 11:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 14:49 IPoIB: Fix multicast packet drops before join is complete Christoph Lameter
2009-06-04 5:41 ` David Miller
2009-06-04 14:28 ` Or Gerlitz
2009-06-04 15:52 ` Christoph Lameter
2009-06-04 22:30 ` David Miller
2009-06-05 14:18 ` Christoph Lameter
2009-06-05 16:56 ` Roland Dreier
2009-06-05 19:17 ` Christoph Lameter
2009-06-05 21:12 ` Roland Dreier
2009-06-06 1:17 ` David Miller
2009-06-05 21:13 ` Roland Dreier
2009-06-08 15:16 ` Christoph Lameter
2009-06-06 1:16 ` David Miller
2009-06-08 15:20 ` Christoph Lameter
2009-06-08 21:29 ` David Miller
2009-06-09 20:52 ` Roland Dreier
2009-06-10 0:45 ` David Miller
2009-06-10 3:55 ` Roland Dreier
2009-06-10 4:57 ` David Miller
2009-06-10 5:04 ` Roland Dreier
2009-06-10 5:12 ` David Miller
2009-06-10 10:18 ` Or Gerlitz
2009-06-10 12:01 ` David Miller
2009-06-11 11:45 ` Or Gerlitz
2009-06-11 11:57 ` David Miller [this message]
2009-06-11 15:07 ` Christoph Lameter
2009-06-11 23:58 ` David Miller
2009-06-12 14:17 ` Christoph Lameter
2009-06-05 16:54 ` Roland Dreier
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=20090611.045721.05821546.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cl@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=rdreier@cisco.com \
--cc=yosefe@voltaire.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).