From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Samuel Maftoul <maftoul@esrf.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS problem
Date: 22 Nov 2001 13:32:45 +0100 [thread overview]
Message-ID: <shsd72bgf4i.fsf@charged.uio.no> (raw)
In-Reply-To: <20011122095251.A18254@pcmaftoul.esrf.fr>
In-Reply-To: <20011122095251.A18254@pcmaftoul.esrf.fr>
>>>>> " " == Samuel Maftoul <maftoul@esrf.fr> writes:
> I thought that NFS's underlying FS do not have any effect on
> NFS performances, and that the client is not aware of the
> ("local") remote FS. Am I wrong ? Does anybody have an idea to
> fix the problem ?
Why do you think that something on the client is 'aware' of the remote
fs?
My guess is that you need to redo your test using a TCP mount for the
Linux machine (that's what your Solaris client is doing). My guess is
that you are hitting a UDP transport reliability problem in the
DirectIO case...
> Is it a bug in NFS's implementation of linux kernel ?
No.
Cheers,
Trond
next prev parent reply other threads:[~2001-11-22 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 8:52 NFS problem Samuel Maftoul
2001-11-22 12:32 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 4:52 Conio sandiago
[not found] <5wdAz-5a0-7@gated-at.bofh.it>
2006-01-18 13:55 ` Bodo Eggert
2006-01-18 14:58 ` Ram Gupta
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=shsd72bgf4i.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=maftoul@esrf.fr \
/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