From: "Krzysztof Olędzki" <ole@ans.pl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Eilon Greenstein <eilong@broadcom.com>
Subject: Re: [RFC] bnx2x: Insane RX rings
Date: Thu, 09 Sep 2010 23:21:01 +0200 [thread overview]
Message-ID: <4C894FBD.2020109@ans.pl> (raw)
In-Reply-To: <1284065105.4782.11.camel@edumazet-laptop>
On 2010-09-09 22:45, Eric Dumazet wrote:
> So I have a small dev machine, 4GB of ram,
> a dual E5540 cpu (quad core, 2 threads per core),
> so a total of 16 threads.
>
> Two ethernet ports, eth0 and eth1,
>
> 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10Gigabit PCIe
> 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10Gigabit PCIe
>
> bnx2x 0000:02:00.0: eth0: using MSI-X IRQs: sp 68 fp[0] 69 ... fp[15] 84
> bnx2x 0000:02:00.1: eth1: using MSI-X IRQs: sp 85 fp[0] 86 ... fp[15] 101
>
>
> Default configuration :
>
> ethtool -g eth0
> Ring parameters for eth0:
> Pre-set maximums:
> RX: 4078
> RX Mini: 0
> RX Jumbo: 0
> TX: 4078
> Current hardware settings:
> RX: 4078
> RX Mini: 0
> RX Jumbo: 0
> TX: 4078
>
> Problem is : With 16 RX queues per device , thats 4078*16*2Kbytes per
> ethernet port.
>
> Total :
>
> skbuff_head_cache 130747 131025 256 15 1 : tunables 120 60 8 : slabdata 8735 8735 40
> size-2048 130866 130888 2048 2 1 : tunables 24 12 8 : slabdata 65444 65444 28
>
> Thats about 300 Mbytes of memory, just in case some network trafic will occur.
>
> Lets do something about that ?
Yep, it is ~8MB per queue, not so much alone, but a lot together. For
this reason I use something like bnx2.num_queues=2 on servers where I
don't need much CPU power for network workload.
Best regards,
Krzysztof Olędzki
next prev parent reply other threads:[~2010-09-09 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 20:45 [RFC] bnx2x: Insane RX rings Eric Dumazet
2010-09-09 21:21 ` Krzysztof Olędzki [this message]
2010-09-09 21:30 ` David Miller
2010-09-09 21:38 ` Rick Jones
2010-09-10 11:16 ` Eilon Greenstein
2010-09-10 15:46 ` Rick Jones
2010-09-10 15:54 ` Rick Jones
2010-09-10 16:42 ` 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=4C894FBD.2020109@ans.pl \
--to=ole@ans.pl \
--cc=eilong@broadcom.com \
--cc=eric.dumazet@gmail.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 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).