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: Thu, 06 May 2010 20:12:02 -0700 [thread overview]
Message-ID: <4BE38502.2000507@candelatech.com> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FEA26A969@rrsmsx501.amr.corp.intel.com>
On 05/06/2010 05:06 PM, Tantilov, Emil S wrote:
> Ben Greear wrote:
>> On 05/06/2010 10:51 AM, Tantilov, Emil S wrote:
>>
>>> Hi Ben,
>>>
>>> We do have a patch in testing (see attached). It may not apply
>>> cleanly as it is on top of some other patches currently in
>>> validation. Let me know if it works for you.
>>
>> It wasn't difficult to backport this patch to 2.6.31.12....
>>
>> I just tested this on an 85998 NIC and 50 MAC-VLANs worked fine.
>>
>> The NIC doesn't show as PROMISC in any way I can detect, but I guess
>> it must actually be in PROMISC mode:
>
> Yes the interface is in promisc mode. The driver sets the FCTRL.UPE bit
> (unicast promisc mode) when the number of allowed rar_entries is exceeded.
Is there any way to get this setting from ethtool or similar? It would be nice
to know the actual PROMISC state of the NIC regardless of what user-space has or has not
configured.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-05-07 3:12 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
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 [this message]
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=4BE38502.2000507@candelatech.com \
--to=greearb@candelatech.com \
--cc=arnd@arndb.de \
--cc=emil.s.tantilov@intel.com \
--cc=kaber@trash.net \
--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 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).