From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Patrick McHardy <kaber@trash.net>,
Mark Smith <lk-netdev@lk-netdev.nosense.org>,
Jarek Poplawski <jarkao2@gmail.com>,
netdev@vger.kernel.org
Subject: Re: UDP is bypassing qdisc statistics ....
Date: Tue, 01 Sep 2009 17:58:05 +0200 [thread overview]
Message-ID: <4A9D448D.6050309@gmail.com> (raw)
In-Reply-To: <4A9D410D.5000507@gmail.com>
Eric Dumazet a écrit :
> Christoph Lameter a écrit :
>> On Tue, 1 Sep 2009, Eric Dumazet wrote:
>>
>>> You should see that in /proc/interrupts, if I correctly understand bnx2.c
>> Hmmm I have 8 interrupts:
>>
>> 62: 158 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-0
>> 63: 84 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-1
>> 64: 412 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-2
>> 65: 25 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-3
>> 66: 49718 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-4
>> 67: 65 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-5
>> 68: 686 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-6
>> 69: 2582 0 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 IR-PCI-MSI-edge eth0-7
>
> Yes, this confirm you have 8 queues on this NIC
>
> Strange thing is they seem to be all serviced by CPU-0, which is not good...
>
>
>
Given that bnx2.c uses num_online_cpus() at init time, you could
as a workaround do the insmod/modprobe bnx2 with only one online cpu,
and you'll revert to a mono-queue NIC :)
int msix_vecs = min(cpus + 1, RX_MAX_RINGS);
...
if ((bp->flags & BNX2_FLAG_MSIX_CAP) && !dis_msi && cpus > 1)
bnx2_enable_msix(bp, msix_vecs);
For your multicast test anyway, only one queue should be used (one flow)
next prev parent reply other threads:[~2009-09-01 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 21:46 UDP is bypassing qdisc statistics Christoph Lameter
2009-08-31 19:54 ` Eric Dumazet
2009-08-31 20:58 ` Mark Smith
2009-09-01 6:37 ` Jarek Poplawski
2009-09-01 7:00 ` Eric Dumazet
2009-09-01 9:37 ` Mark Smith
2009-09-01 18:03 ` Christoph Lameter
2009-09-01 14:20 ` Patrick McHardy
2009-09-01 14:58 ` Eric Dumazet
2009-09-01 19:05 ` Christoph Lameter
2009-09-01 15:28 ` Eric Dumazet
2009-09-01 19:35 ` Christoph Lameter
2009-09-01 15:43 ` Eric Dumazet
2009-09-01 15:58 ` Eric Dumazet [this message]
2009-09-01 20:13 ` Christoph Lameter
2009-09-01 21:55 ` Christoph Lameter
2009-09-01 20:24 ` Jarek Poplawski
2009-09-02 1:36 ` Christoph Lameter
2009-09-01 18:29 ` Christoph Lameter
2009-09-01 19:30 ` Christoph Lameter
2009-09-01 15:34 ` Eric Dumazet
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=4A9D448D.6050309@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=cl@linux-foundation.org \
--cc=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=lk-netdev@lk-netdev.nosense.org \
--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.