From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Simon Matthews <simon@paxonet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS Client mis-behaviour?
Date: 11 Jun 2002 16:31:00 +0200 [thread overview]
Message-ID: <shs8z5lanvf.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0206102041020.11116-100000@spare>
>>>>> " " == Simon Matthews <simon@paxonet.com> writes:
> Solution: the Ethernet interface was connected to a switch that
> only supports half-duplex connecting to a full-duplex switch
> solved the problem. However, it does seem that the NFS client
> was not handling the situation well.
The NFS client neither knows nor cares what is going on down in the
ethernet layer. As far as it is concerned, you might as well be using
semaphore to pass messages between the computers.
All the NFS client needs to know is that it should retry the socket
sendmsg() operation when a certain (user defined) timeout value is
reached.
Cheers,
Trond
next prev parent reply other threads:[~2002-06-11 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 3:48 NFS Client mis-behaviour? Simon Matthews
2002-06-11 5:14 ` Andreas Dilger
2002-06-11 14:31 ` Trond Myklebust [this message]
2002-06-11 16:28 ` Simon Matthews
2002-06-12 11:57 ` Trond Myklebust
2002-06-12 8:16 ` Alan Cox
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=shs8z5lanvf.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@paxonet.com \
/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