From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: 10 G eth (10000) on Gentoo
Date: Fri, 2 Sep 2011 15:29:50 +0000 (UTC) [thread overview]
Message-ID: <loom.20110902T172502-327@post.gmane.org> (raw)
In-Reply-To: CAC=wYCF0Vn58QNSdjvqrqOVYCAj1V+pUJvkPTMwzGTxhrBTc1w@mail.gmail.com
Adam Carter <adamcarter3 <at> gmail.com> writes:
> Looks like intel made multiqueue available in Nov. 2010. You can set
> up to 16 queues.
> http://downloadmirror.intel.com/14687/eng/README.txt
Thanks guys, for the discussion. Kinda reminds me back in
in the day of "jumbo frames" and the arguments as to if/when
jumbo frame support helps in routing.....
Any anecdotal comments as to how poor-bad 10 G eth crawls/fails
on a Microsoft server, would give me ammo to shoot down
the opposition...
James
next prev parent reply other threads:[~2011-09-02 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 13:08 [gentoo-user] 10 G eth (10000) on Gentoo James
2011-08-31 23:58 ` Adam Carter
2011-09-01 1:43 ` Michael Mol
2011-09-01 1:46 ` Adam Carter
2011-09-01 6:48 ` Adam Carter
2011-09-02 15:29 ` James [this message]
2011-09-02 18:09 ` [gentoo-user] " Michael Mol
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=loom.20110902T172502-327@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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