From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: unstable 10GBE performance with recent kernels (> 3.0.X)
Date: Mon, 18 Jun 2012 15:07:53 +0200 [thread overview]
Message-ID: <4FDF2829.6050705@profihost.ag> (raw)
In-Reply-To: <1340023876.7491.1153.camel@edumazet-glaptop>
Am 18.06.2012 14:51, schrieb Eric Dumazet:
> On Mon, 2012-06-18 at 14:36 +0200, Stefan Priebe - Profihost AG wrote:
>> Am 18.06.2012 12:25, schrieb Eric Dumazet:
>>> I would remove all this (pretty old and obsolete) stuff and use
standard
>>> params.
>> OK, thanks. done.
>>
>> I've one RHEL6 system (using default 2.6.32 kernel) where only using
>> "ntuple on" results in just 4-5Gbit/s while the others using 3.5.0-rc2
>> are working fine.
>>
>
> OK, then you might play with affinities, that's the only thing that
> might need sysadmin tuning (irqbalance needs to be disabled)
I've now used this one:
# script provided by intel
/root/set_irq_affinity.sh eth2
ifconfig eth2 mtu 9000
ethtool -K eth2 ntuple on
irqbalance is off
But with the latest long term stable vanilla kernel 3.0.34.
# iperf -c HOST -t 60
works fine but with -d for using both directions i see around 9.8Gbit/s
in one direction and only 300kb/s in the other direction.
Stefan
next prev parent reply other threads:[~2012-06-18 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 9:22 unstable 10GBE performance with recent kernels (> 3.0.X) Stefan Priebe - Profihost AG
2012-06-18 9:45 ` Eric Dumazet
2012-06-18 10:05 ` Stefan Priebe - Profihost AG
2012-06-18 10:25 ` Eric Dumazet
2012-06-18 12:36 ` Stefan Priebe - Profihost AG
2012-06-18 12:51 ` Eric Dumazet
2012-06-18 13:07 ` Stefan Priebe - Profihost AG [this message]
2012-06-18 13:29 ` Eric Dumazet
2012-06-18 14:17 ` Stefan Priebe - Profihost AG
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=4FDF2829.6050705@profihost.ag \
--to=s.priebe@profihost.ag \
--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