From: Jay Vosburgh <fubar@us.ibm.com>
To: vyasevic@redhat.com
Cc: Or Gerlitz <or.gerlitz@gmail.com>,
Shawn Bohrer <shawn.bohrer@gmail.com>,
netdev@vger.kernel.org, Hadar Hen Zion <hadarh@mellanox.com>,
Amir Vadai <amirv@mellanox.com>, Jiri Pirko <jiri@resnulli.us>
Subject: Re: 3.10.0-rc2 mlx4 not receiving packets for some multicast groups
Date: Thu, 30 May 2013 17:23:20 -0700 [thread overview]
Message-ID: <20365.1369959800@death.nxdomain> (raw)
In-Reply-To: <51A7BD42.8060504@redhat.com>
Vlad Yasevich <vyasevic@redhat.com> wrote:
>>> CC: Jiri Pirko <jiri@resnulli.us>
>>> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
>>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>>
>>> I've confirmed that reverting this patch on top of 3.10-rc3 allows me
>>> to receive packets on all of my multicast groups without the Mellanox
>>> high_rate_steer option set.
>>
>> OK, impressive debugging... so what do we do from here? Vlad, Shawn
>> observes a regression once this patch is used on a large scale setup
>> that uses many multicast groups (you can read the posts done earlier
>> on this thread), does this rings any bell w.r.t to the actual problem
>> in the patch?
>
>I haven't seen that, but I didn't test with that many multicast groups. I
>had 20 groups working.
>
>I'll take a look and see what might be going on.
I've actually been porting bonding to the dev_sync/unsync
system, and have a patch series of 4 fixes to various internals of
dev_sync/unsync; I'll post those under separate cover. It may be that
one or more of those things are the source of this problem (or I might
have it all wrong).
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2013-05-31 0:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 15:49 3.10.0-rc2 mlx4 not receiving packets for some multicast groups Shawn Bohrer
2013-05-24 16:34 ` Shawn Bohrer
2013-05-24 16:58 ` Eric Dumazet
2013-05-25 3:41 ` Or Gerlitz
2013-05-25 15:13 ` Shawn Bohrer
2013-05-25 19:41 ` Or Gerlitz
2013-05-25 21:37 ` Shawn Bohrer
2013-05-28 20:15 ` Shawn Bohrer
2013-05-29 13:55 ` Or Gerlitz
2013-05-30 20:31 ` Shawn Bohrer
2013-05-30 20:42 ` Or Gerlitz
2013-05-30 20:57 ` Vlad Yasevich
2013-05-31 0:23 ` Jay Vosburgh [this message]
2013-05-31 15:17 ` Shawn Bohrer
2013-05-25 3:49 ` Or Gerlitz
2013-05-25 14:02 ` Shawn Bohrer
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=20365.1369959800@death.nxdomain \
--to=fubar@us.ibm.com \
--cc=amirv@mellanox.com \
--cc=hadarh@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=shawn.bohrer@gmail.com \
--cc=vyasevic@redhat.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 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.