netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Michel Hautbois <jhautbois@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Difficulties to get 1Gbps on be2net ethernet card
Date: Wed, 30 May 2012 08:51:53 +0200	[thread overview]
Message-ID: <CAL8zT=h2hoTWDMpTe8P-xfm-USXD6spx8fFVmm1UXyOfuuqhZw@mail.gmail.com> (raw)
In-Reply-To: <1338360536.2760.85.camel@edumazet-glaptop>

2012/5/30 Eric Dumazet <eric.dumazet@gmail.com>:
> On Wed, 2012-05-30 at 08:28 +0200, Jean-Michel Hautbois wrote:
>
>> If this can help, setting tx queue length to 5000 seems to make the
>> problem disappear.
>
> Then you should have drops at Qdisc layer (before your change to 5000)
>
> tc -s -d qdisc
>
>> I didn't specified it : MTU is 4096, UDP packets are 4000 bytes.
>

Yes :
qdisc mq 0: dev eth1 root
 Sent 5710049154383 bytes 1413544639 pkt (dropped 73078, overlimits 0
requeues 281540)
 backlog 0b 0p requeues 281540

Why ? With a 2.6.26 kernel it works well with a tx queue length of 1000.

  reply	other threads:[~2012-05-30  6:52 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 [this message]
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
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='CAL8zT=h2hoTWDMpTe8P-xfm-USXD6spx8fFVmm1UXyOfuuqhZw@mail.gmail.com' \
    --to=jhautbois@gmail.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).