From: Greg Banks <gnb@sgi.com>
To: Muhammad Irfan Nazir <arfan.se@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS behavior as seen by EXT2
Date: Tue, 20 Dec 2005 10:14:32 +1100 [thread overview]
Message-ID: <20051219231432.GA30403@sgi.com> (raw)
In-Reply-To: <28437eef0512190352l34a0ba47g96be56cb455608cf@mail.gmail.com>
On Mon, Dec 19, 2005 at 04:52:30PM +0500, Muhammad Irfan Nazir wrote:
> Where as at EXT2 level I was supposing to get the position zero as the file
> was closed in the last reading and all its memory references were deleted.
>
> How/where does the nfs keeps the record of the previous reading position?
In the NFS client. Each READ call passes the filehandle, offset and
size to be read. On traditional UNIX servers, read and readahead
behaviour is controlled entirely by the client. However the Linux
NFS server also keeps a cache of read-ahead state for a small number
of files (search for "raparm" in fs/nfsd/vfs.c) thus enabling it to
do server-side readahead also.
> I want to get the reference to the documentation stating the read/write
> behaviour of nfs.
RFC1813 would be a good start.
http://www.faqs.org/rfcs/rfc1813.html
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-12-19 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 11:52 NFS behavior as seen by EXT2 Muhammad Irfan Nazir
2005-12-19 23:14 ` Greg Banks [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=20051219231432.GA30403@sgi.com \
--to=gnb@sgi.com \
--cc=arfan.se@gmail.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.