From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] myricom 10gbe update
Date: Wed, 23 Sep 2009 22:56:24 -0400 [thread overview]
Message-ID: <353050cb05a3de49e8d78bd31494e3ee@brasstown.quanstro.net> (raw)
with the help of the great folks at myricom, we've
been able to find a couple of performance limitations
and fix a few bugs. we were able to transfer aoe at >1GB/s
between two modest (3 year old) 1.86ghz intel 5000 xeons.
contrib quanstro/etherm10g
this patch uses the vmappat patch which is now out-of-date.
a redo is available at /n/sources/contrib/quanstro/patredux.
this patch is not required but helps if you are using "small"
packets. by small, i mean < 8k. to remove, just turn vmappat
to vmap without the 3d arg.
since we are not using msi interrupts, the coal parameter
(interrupt coalesing) is fairly sensitve. this is because the
dance even mp interrupts need to do takes many cycles.
it's amazing how many apics, i/o apics and other nonsense
is involved on a modern pcie machine. i have used values
from 15-50µs with the current code. ymmv.
- erik
reply other threads:[~2009-09-24 2:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=353050cb05a3de49e8d78bd31494e3ee@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).