From: Patrick McHardy <kaber@trash.net>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: ixgbe and mac-vlans problem
Date: Fri, 30 Apr 2010 14:24:23 +0200 [thread overview]
Message-ID: <4BDACBF7.4050307@trash.net> (raw)
In-Reply-To: <4BDA07DB.8020206@candelatech.com>
Ben Greear wrote:
> Hello!
>
> We are seeing a strange problem with mac-vlans on top of an 82599 NIC
> (ixgbe)
> on a 2.6.31.y (plus patches) kernel.
>
> Basically, we create 50 mac-vlans, with sequential MAC addresses and
> sequential
> IP addresses, and set up ip rules properly.
>
> The issue is that only 10 or so of the mac-vlans receive other than
> broadcast packets. The ixgbe NIC doesn't show PROMISC mode.
Not showing PROMISC is normal since this is going into promisc
when too many unicast addresses are configured is handled internally
by the drivers.
> If we manually turn on PROMISC mode on the physical ixgbe interface,
> then everything works properly. I'm guessing the ixgbe NIC must
> have some filters that mac-vlan is trying to enable w/out turning on
> full PROMISC mode. Is there any easy way to debug these filters
> to see if they are being properly configured?
Adding "#define DEBUG" to ixgbe_common.c should print some information
when unicast addresses are added.
next prev parent reply other threads:[~2010-04-30 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 22:27 ixgbe and mac-vlans problem Ben Greear
2010-04-30 12:24 ` Patrick McHardy [this message]
2010-04-30 18:00 ` Arnd Bergmann
2010-04-30 18:09 ` Ben Greear
2010-04-30 21:13 ` Tantilov, Emil S
2010-04-30 22:04 ` Ben Greear
2010-04-30 22:20 ` Ben Greear
2010-04-30 22:26 ` Tantilov, Emil S
2010-05-06 16:23 ` Ben Greear
2010-05-06 17:51 ` Tantilov, Emil S
2010-05-06 20:49 ` Ben Greear
2010-05-07 0:06 ` Tantilov, Emil S
2010-05-07 3:12 ` Ben Greear
2010-05-07 17:40 ` Tantilov, Emil S
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=4BDACBF7.4050307@trash.net \
--to=kaber@trash.net \
--cc=greearb@candelatech.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 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.