From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mark Price <mkprice@us.ibm.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: wsize & PAGE_SIZE issues on IA64 clients.
Date: 28 Mar 2003 00:57:43 +0100 [thread overview]
Message-ID: <shsr88sl5vs.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0303271219410.2496-100000@mprice-laptop.beaverton.ibm.com>
>>>>> " " == Mark Price <mkprice@us.ibm.com> writes:
> Can someone give me rough explanation of why that logic is
> used? ie. Why the page is written synchronously if its smaller
> than the page size? and Why even when its written synchronously
> the wsize wasn't used, but the remote filesystems block size
> was used?
1) Because in order to write asynchronously you would have to have
more than 1 outstanding request per page. The locking models all
assume only 1 request / page.
2) 'cos the servers get upset if we deliberately allow you to do
things that violate the protocol.
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-27 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 21:24 wsize & PAGE_SIZE issues on IA64 clients Mark Price
2003-03-27 23:57 ` Trond Myklebust [this message]
2003-03-31 19:09 ` Greg Lindahl
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 0:01 Lever, Charles
2003-03-31 23:25 Lever, Charles
2003-03-31 23:46 ` Mark Price
2003-04-01 5:48 ` Trond Myklebust
2003-04-01 6:11 ` Mark Price
2003-04-01 6:25 ` Trond Myklebust
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=shsr88sl5vs.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=mkprice@us.ibm.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.