From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS Client Performance Question
Date: Wed, 13 Jul 2005 16:40:03 -0400 [thread overview]
Message-ID: <111aefd050713134026ad13df@mail.gmail.com> (raw)
In-Reply-To: <1121285771.8234.7.camel@lade.trondhjem.org>
On 7/13/05, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> on den 13.07.2005 Klokka 14:30 (-0400) skreiv Chris Penney:
> > The client mount options are:
> > rw,nosuid,bg,hard,intr,nfsvers=3D3,tcp,rsize=3D32768,wsize=3D32768
>=20
> Does this match the entry for this mountpoint in /proc/mounts ?
Yes, and if I do a streaming write test I do in fact see only 32k
async writes even with '-r 4k'.
The entry is:
server:/s on /s/nicfs5 type nfs
(rw,nosuid,bg,hard,intr,nfsvers=3D3,tcp,rsize=3D32768,wsize=3D32768,addr=3D=
1.1.1.1)
Chris
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-13 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 18:30 NFS Client Performance Question Chris Penney
2005-07-13 20:16 ` Trond Myklebust
2005-07-13 20:40 ` Chris Penney [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 18:44 Lever, Charles
2005-07-13 18:55 ` Chris Penney
2005-07-13 19:09 ` Peter Staubach
2005-07-13 19:57 ` Chris Penney
2005-07-13 19:04 Lever, Charles
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=111aefd050713134026ad13df@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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.