From: David Miller <davem@davemloft.net>
To: cl@linux-foundation.org
Cc: rdreier@cisco.com, netdev@vger.kernel.org, yosefe@Voltaire.COM
Subject: Re: IPoIB: Fix multicast packet drops before join is complete
Date: Thu, 11 Jun 2009 16:58:56 -0700 (PDT) [thread overview]
Message-ID: <20090611.165856.108387598.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0906111107390.29827@gentwo.org>
From: Christoph Lameter <cl@linux-foundation.org>
Date: Thu, 11 Jun 2009 11:07:52 -0400 (EDT)
> On Tue, 9 Jun 2009, David Miller wrote:
>
>> From: Roland Dreier <rdreier@cisco.com>
>> Date: Tue, 09 Jun 2009 20:55:57 -0700
>>
>> > Hmm... how do I do that? The interface gets an skb that it sees should
>> > be sent to a multicast group that it is not a member of yet, and so it
>> > fires off a request to join that group (as a send-only member). How
>> > does a netdev block the process that queued up a given skb to send?
>> > Couldn't the packet have come through a local software bridge or
>> > something like that, so the original process is long since lost to the
>> > network stack?
>>
>> If a facility doesn't exist yet, we're going to have to create
>> one. It would need to do a downcall to the device when the
>> user joins a multicast group on a socket, and then the device
>> can do whatever magic is necessary to speak multicast immediately
>> and sleep until it really is available for immediate use.
>
> Umm?? My patch does that....
No it does not. It eliminates a limit on the generic intermediate
queue. It did no blocking, no sleeping, or the process when it
joined the group.
I was suggesting to block the process, at socket context time, when it
joins a multicast group. That way it wouldn't be able to do any sends
until IPoIB could resolve the multicast join.
next prev parent reply other threads:[~2009-06-11 23:58 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
2009-06-11 15:07 ` Christoph Lameter
2009-06-11 23:58 ` David Miller [this message]
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.165856.108387598.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cl@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--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).