From: Ben Greear <greearb@candelatech•com>
To: "Tantilov, Emil S" <emil.s.tantilov@intel•com>
Cc: Arnd Bergmann <arnd@arndb•de>, NetDev <netdev@vger•kernel.org>,
Patrick McHardy <kaber@trash•net>
Subject: Re: ixgbe and mac-vlans problem
Date: Fri, 30 Apr 2010 15:04:59 -0700 [thread overview]
Message-ID: <4BDB540B.3080005@candelatech.com> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FE55609F0@rrsmsx501.amr.corp.intel.com>
On 04/30/2010 02:13 PM, Tantilov, Emil S wrote:
>> I will double-check the NIC chipset on the system that showed the
>> problem yesterday.
>
> I ran a quick test in my setup with 82599 and was able to pass traffic
> on all 50 mac-vlans without issues. This is on net-next.
I attempted this on an 82598 system, and it reproduces the problem
for me, so I think that must be what the customer was using as well
(I haven't gotten access to their system again, yet)
I created 50 mac-vlans on eth11, but it does NOT go PROMISC
mode as far as I can tell. Only 14 of the mac-vlans are
working. I'm using 64kbps UDP streams, 1k packets (ie, light load).
[root@i7-1qc-1 lanforge]# cat /sys/class/net/eth11/flags
0x1003
[root@i7-1qc-1 lanforge]# ip link show dev eth11
2: eth11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:e0:ed:11:25:12 brd ff:ff:ff:ff:ff:ff
I put it into promisc mode and now they all work:
[root@i7-1qc-1 lanforge]# ip link show dev eth11
2: eth11: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:e0:ed:11:25:12 brd ff:ff:ff:ff:ff:ff
[root@i7-1qc-1 lanforge]# cat /sys/class/net/eth11/flags
0x1103
This is on a slightly modified 2.6.31.12 kernel. I haven't had a chance to try
this on a more recent kernel yet.
lspci:
03:00.0 Ethernet controller: Intel Corporation 82598EB 10 Gigabit AF Dual Port Network Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82598EB 10 Gigabit AF Dual Port Network Connection
Please let me know if I can offer any additional information. It will probably take a few days before I can
get the .34 kernel in testing.
Thanks,
Ben
--
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-04-30 22:05 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
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 [this message]
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=4BDB540B.3080005@candelatech.com \
--to=greearb@candelatech$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=emil.s.tantilov@intel$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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