From: Olaf Kirch <okir@suse.de>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Brett Petrusek <brettp@aspsys.com>, nfs@lists.sourceforge.net
Subject: Re: IA64 Server / IA32 Client problem
Date: Tue, 2 Aug 2005 17:27:04 +0200 [thread overview]
Message-ID: <20050802152704.GH29054@suse.de> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C611308539E55@lavender-fe.eng.netapp.com>
On Tue, Aug 02, 2005 at 07:36:17AM -0700, Lever, Charles wrote:
> can you tell us about the file system on the ia64 server. block size,
> fstype, etc?
>
> what's the page size on that system?
This pretty much matches the symptoms we've seen with SGI servers
on 2.6.5. You may want to try a recent kernel on your clients, which
has support for write sizes larger than the client's PAGE_CACHE_SIZE.
Exactly these bad performance numbers made us backport the large
wsize/rsize patches to 2.6.5 for SLES.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-08-02 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 14:36 IA64 Server / IA32 Client problem Lever, Charles
2005-08-02 15:27 ` Olaf Kirch [this message]
2005-08-02 15:37 ` Brett Petrusek
-- strict thread matches above, loose matches on Subject: below --
2005-07-20 22:37 IA64 Server / IA32 Client Problem Brett Petrusek
2005-07-21 19:29 ` Dan Stromberg
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=20050802152704.GH29054@suse.de \
--to=okir@suse.de \
--cc=Charles.Lever@netapp.com \
--cc=brettp@aspsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox