From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: davem@davemloft.net, eilong@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] bnx2x: Support for managing RX indirection table
Date: Thu, 17 Feb 2011 10:09:24 +0100 [thread overview]
Message-ID: <1297933764.2670.20.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1102161210190.31937@pokey.mtv.corp.google.com>
Le mercredi 16 février 2011 à 12:27 -0800, Tom Herbert a écrit :
> Support fetching and retrieving RX indirection table via ethtool.
>
> Signed-off-by: Tom Herbert <therbert@google.com>
> ---
> drivers/net/bnx2x/bnx2x.h | 2 +
> drivers/net/bnx2x/bnx2x_ethtool.c | 56 +++++++++++++++++++++++++++++++++++++
> drivers/net/bnx2x/bnx2x_main.c | 22 +++++++++++---
> 3 files changed, 75 insertions(+), 5 deletions(-)
Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
As this is a bit unusual stuff (ethtool -X), I guess some hints can be
useful to testers and admins :
I tested this patch on my dev machine
Broadcom Corporation NetXtreme II BCM57711E 10Gigabit PCIe
(Hewlett-Packard Company NC532i Dual Port 10GbE Multifunction BL-C
Adapter)
# ethtool -X eth1 weight 0 1 0 2 0 4 0 8 0 16 0 32
# ethtool -x eth1
RX flow hash indirection table for eth1 with 16 RX ring(s):
0: 1 1 3 3 3 3 5 5
8: 5 5 5 5 5 5 7 7
16: 7 7 7 7 7 7 7 7
24: 7 7 7 7 7 7 9 9
32: 9 9 9 9 9 9 9 9
40: 9 9 9 9 9 9 9 9
48: 9 9 9 9 9 9 9 9
56: 9 9 9 9 9 9 11 11
64: 11 11 11 11 11 11 11 11
72: 11 11 11 11 11 11 11 11
80: 11 11 11 11 11 11 11 11
88: 11 11 11 11 11 11 11 11
96: 11 11 11 11 11 11 11 11
104: 11 11 11 11 11 11 11 11
112: 11 11 11 11 11 11 11 11
120: 11 11 11 11 11 11 11 11
After some (distributed) trafic on eth1 I get :
[root@svivoipvnx021 ~]# ethtool -S eth1|grep rx_ucast_packets
[0]: rx_ucast_packets: 62
[1]: rx_ucast_packets: 15870
[2]: rx_ucast_packets: 9
[3]: rx_ucast_packets: 31507
[4]: rx_ucast_packets: 0
[5]: rx_ucast_packets: 63106
[6]: rx_ucast_packets: 0
[7]: rx_ucast_packets: 122051
[8]: rx_ucast_packets: 1
[9]: rx_ucast_packets: 248071
[10]: rx_ucast_packets: 0
[11]: rx_ucast_packets: 519864
[12]: rx_ucast_packets: 0
[13]: rx_ucast_packets: 0
[14]: rx_ucast_packets: 0
[15]: rx_ucast_packets: 0
rx_ucast_packets: 1000541
next prev parent reply other threads:[~2011-02-17 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 20:27 [PATCH v2] bnx2x: Support for managing RX indirection table Tom Herbert
2011-02-17 9:09 ` Eric Dumazet [this message]
2011-02-17 12:58 ` Eilon Greenstein
2011-02-17 20:49 ` David Miller
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=1297933764.2670.20.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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