From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: Douglas Furlong <douglas.furlong@firebox.com>, nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: 28 Nov 2003 11:56:25 -0500 [thread overview]
Message-ID: <shsptfch1om.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0311281257130.22389-100000@kenzo.iwr.uni-heidelberg.de>
>>>>> " " == Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de> writes:
> I also see something like 0.8-1% retransmissions and these
> messages on newly installed Fedora Core 1 on some cluster
> nodes, using default r/wsize (8192). As I'm using root-NFS, the
> node is quite useless when this situation happens. I'm sure
Huh? Why should a 1% retransmission make a noticable difference? Be
realistic: we're talking about a delay of 100ms on 1/100 requests...
I get ~2% retransmission rate when I do UDP loopback mounts without
seeing any problems at all: it still compares well to the same mount
using TCP.
Now it may be that the Fedora kernel has some other crap in it that is
screwing up interrupts & other such things (NAPI perhaps?). Has
anybody that is seeing these problems made a comparison with an
equivalent stock Marcelo kernel?
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-28 16:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07 ` Douglas Furlong
2003-11-27 20:02 ` Trond Myklebust
2003-11-28 8:46 ` Juergen Sauer
2003-11-28 9:37 ` Douglas Furlong
2003-11-28 10:11 ` Juergen Sauer
2003-11-28 10:48 ` Douglas Furlong
2003-11-28 12:28 ` Bogdan Costescu
2003-11-28 16:56 ` Trond Myklebust [this message]
2003-11-28 18:43 ` Bogdan Costescu
2003-12-02 14:37 ` Douglas Furlong
2003-12-02 15:37 ` Trond Myklebust
2003-12-04 17:17 ` Steve Dickson
2003-12-04 17:37 ` Steve Dickson
2003-12-04 18:39 ` Trond Myklebust
2003-12-04 19:11 ` Steve Dickson
2003-12-04 20:55 ` seth vidal
2003-12-04 21:24 ` Steve Dickson
2003-12-05 2:53 ` Kyle Rose
2003-12-09 19:47 ` Steve Dickson
2003-12-09 20:09 ` Kyle Rose
2003-12-05 15:50 ` Bogdan Costescu
2003-11-30 20:01 ` seth vidal
2003-12-01 10:58 ` Bogdan Costescu
2003-11-28 12:36 ` Bogdan Costescu
-- strict thread matches above, loose matches on Subject: below --
2009-05-16 0:57 nfs: " Jerome Walters
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=shsptfch1om.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=douglas.furlong@firebox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox