From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: stable 10GBE under 3.4.2 or 3.5.0-rc2
Date: Mon, 18 Jun 2012 09:40:47 +0200 [thread overview]
Message-ID: <4FDEDB7F.4070600@profihost.ag> (raw)
Hi list,
i've still problems with stable network speed under recent kernels. With
3.0.32 i get stable 9.90 Gbit/s in both directions. With 3.4.2 or
3.5.0-rc2 it drops sometimes down to around 1 Gbit/s. Sadly i've no idea
when this happen? It works sometimes for minutes at 9.9Gbit/s and then
suddently only with 3-4Gbit/s or even 1Gbit/s using recent kernels.
I'm using various tunings recommanded by intel (Improving Performance)
=> http://downloadmirror.intel.com/5874/eng/README.txt
Has anybody a hint for me or additional settings intel does not mention?
Stefan
next reply other threads:[~2012-06-18 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 7:40 Stefan Priebe - Profihost AG [this message]
2012-06-18 8:11 ` stable 10GBE under 3.4.2 or 3.5.0-rc2 Alexandre DERUMIER
2012-06-18 9:11 ` Stefan Priebe - Profihost AG
2012-06-18 9:21 ` Alexandre DERUMIER
2012-06-18 9:25 ` Stefan Priebe - Profihost AG
2012-06-18 9:27 ` Alexandre DERUMIER
2012-06-18 13:56 ` Mark Nelson
2012-06-18 14:03 ` 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=4FDEDB7F.4070600@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@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