All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: penney@msu.edu
Cc: "Lever, Charles" <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: NFS Client Performance Question
Date: Wed, 13 Jul 2005 15:09:50 -0400	[thread overview]
Message-ID: <42D566FE.3060300@redhat.com> (raw)
In-Reply-To: <111aefd05071311553ac3d52a@mail.gmail.com>

Chris Penney wrote:

>The Itanium page size is 16k (unless I'm mistaken) and the r/wsize is
>32k so can that still be it?  Or are you saying that it is because the
>size of the write is only 4k?
>

Well, it is curious that the over the wire WRITE requests are still only 4K.
The Sun server is not restricting the transfer sizes, so apparently 
something
else is.

You say that the application on the client is doing random, 4K writes to
the file?  Is the file opened with O_SYNC or anything special like that?

    Thanx...

       ps


-------------------------------------------------------
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

  reply	other threads:[~2005-07-13 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 18:44 NFS Client Performance Question Lever, Charles
2005-07-13 18:55 ` Chris Penney
2005-07-13 19:09   ` Peter Staubach [this message]
2005-07-13 19:57     ` Chris Penney
  -- strict thread matches above, loose matches on Subject: below --
2005-07-13 19:04 Lever, Charles
2005-07-13 18:30 Chris Penney
2005-07-13 20:16 ` Trond Myklebust
2005-07-13 20:40   ` Chris Penney

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=42D566FE.3060300@redhat.com \
    --to=staubach@redhat.com \
    --cc=Charles.Lever@netapp.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.