From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: Sathya.Perla@emulex.com, netdev@vger.kernel.org
Subject: Re: Difficulties to get 1Gbps on be2net ethernet card
Date: Fri, 08 Jun 2012 10:22:39 +0200 [thread overview]
Message-ID: <1339143759.6001.53.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAL8zT=jPUEF62-V_0n9o3=n2Mo6y4M_kGgK+OwdXg0aLDazDgQ@mail.gmail.com>
On Fri, 2012-06-08 at 10:14 +0200, Jean-Michel Hautbois wrote:
> 2012/6/8 Eric Dumazet <eric.dumazet@gmail.com>:
> > On Thu, 2012-06-07 at 14:54 +0200, Jean-Michel Hautbois wrote:
> >
> >> eth1 Link encap:Ethernet HWaddr 68:b5:99:b9:8d:d4
> >> UP BROADCAST RUNNING SLAVE MULTICAST MTU:4096 Metric:1
> >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:15215387 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:0 (0.0 B) TX bytes:61476524359 (57.2 GiB)
> >
> >> qdisc mq 0: dev eth1 root
> >> Sent 61476524359 bytes 15215387 pkt (dropped 45683472, overlimits 0
> >> requeues 17480)
> >
> > OK, and "tc -s -d cl show dev eth1"
> >
> > (How many queues are really used)
> >
> >
> >
>
> tc -s -d cl show dev eth1
> class mq :1 root
> Sent 9798071746 bytes 2425410 pkt (dropped 3442405, overlimits 0 requeues 2747)
> backlog 0b 0p requeues 2747
> class mq :2 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :3 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :4 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :5 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :6 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :7 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> class mq :8 root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
Do you have the same distribution on old kernels as well ?
(ie only queue 0 is used)
next prev parent reply other threads:[~2012-06-08 8:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 14:46 Difficulties to get 1Gbps on be2net ethernet card Jean-Michel Hautbois
2012-05-30 6:28 ` Jean-Michel Hautbois
2012-05-30 6:48 ` Eric Dumazet
2012-05-30 6:51 ` Jean-Michel Hautbois
2012-05-30 7:06 ` Eric Dumazet
2012-05-30 7:25 ` Jean-Michel Hautbois
2012-05-30 9:40 ` Jean-Michel Hautbois
2012-05-30 9:56 ` Eric Dumazet
2012-05-30 10:06 ` Jean-Michel Hautbois
2012-05-30 10:04 ` Sathya.Perla
2012-05-30 10:07 ` Jean-Michel Hautbois
2012-06-06 10:04 ` Jean-Michel Hautbois
2012-06-06 11:01 ` Eric Dumazet
2012-06-06 12:34 ` Jean-Michel Hautbois
2012-06-06 13:07 ` Jean-Michel Hautbois
2012-06-06 14:36 ` Jean-Michel Hautbois
2012-06-07 12:27 ` Jean-Michel Hautbois
2012-06-07 12:31 ` Eric Dumazet
2012-06-07 12:54 ` Jean-Michel Hautbois
2012-06-08 6:08 ` Eric Dumazet
2012-06-08 8:14 ` Jean-Michel Hautbois
2012-06-08 8:22 ` Eric Dumazet [this message]
2012-06-08 14:53 ` Jean-Michel Hautbois
2012-06-12 8:24 ` Jean-Michel Hautbois
2012-06-12 8:55 ` Eric Dumazet
2012-06-12 9:01 ` Jean-Michel Hautbois
2012-06-12 9:06 ` Eric Dumazet
2012-06-12 9:10 ` Jean-Michel Hautbois
2012-05-30 10:30 ` Eric Dumazet
2012-05-30 11:10 ` Sathya.Perla
2012-05-31 6:54 ` Jean-Michel Hautbois
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=1339143759.6001.53.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=Sathya.Perla@emulex.com \
--cc=jhautbois@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