From: Romain Dolbeau <romain.dolbeau@caps-entreprise.com>
To: nfs@lists.sourceforge.net
Subject: Re: Latency problem with some clients but not others
Date: Thu, 16 Aug 2007 09:24:24 +0200 [thread overview]
Message-ID: <46C3FBA8.7020905@caps-entreprise.com> (raw)
In-Reply-To: <6E56E676C9D6A74EBC980144BC06A17D04BB45E4@mailbox03.lucas.alllucas.com>
Eli Stair wrote:
> If I entirely misunderstood your post, and you're having problems with
> the 8169 systems, not the intel Xeon with e1000, you might want to
> seriously consider ditching the Realtek (8169) and test with another
> card in that problematic system. Easiest and most direct way to test.
I must not have been very clear, because the other anwser
also suggested fo tix the Intel, which works just fine ;-)
The problem seems indeed to be the realtek crap^H^H^Hard,
as replacing it with an old 3com card brought by a colleague,
the problem just go away.
I'll try fiddling with ethtool and if it fails, I'll just
have to buy a bunch of decent PCI cards :-(
Thanks to all for your help,
--
Romain Dolbeau
<romain.dolbeau@caps-entreprise.com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-08-16 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 17:19 Latency problem with some clients but not others Romain Dolbeau
2007-08-15 17:40 ` Tom Tucker
2007-08-15 17:58 ` Eli Stair
2007-08-16 7:24 ` Romain Dolbeau [this message]
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=46C3FBA8.7020905@caps-entreprise.com \
--to=romain.dolbeau@caps-entreprise.com \
--cc=nfs@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.