From: Greg Banks <gnb@melbourne.sgi.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: James Pearson <james-p@moving-picture.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
nfs@lists.sourceforge.net
Subject: Re: Different NFSSVC_MAXBLKSIZE for udp and tcp clients?
Date: Thu, 27 Nov 2003 11:21:07 +1100 [thread overview]
Message-ID: <3FC54373.EC448BB1@melbourne.sgi.com> (raw)
In-Reply-To: 16325.9710.935587.140271@notabene.cse.unsw.edu.au
Neil Brown wrote:
>
> request size is completely under the control of the client via rsize
> and wsize (except that you cannot exceed the server's maximum).
The point is that the server's maximum is too low, at least when
the client and server are powerful machines with a clean network
between them (i.e. a significant part of SGI's customers).
When I say too low, I have two separate issues:
1. wsize<16K means an Altix client does synchronous writes, which
results in a catastrophic performance hit (writes proceed at
no more than 0.7% of line rate on gige). This is a hot issue
right now.
2. Experience with IRIX shows that (up to a point) better performance
can be achieved for some loads with larger transfer sizes. On
IRIX that point is beyond Linux' current hardcoded maximums. This
is more of a long-term issue.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-27 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 17:34 Different NFSSVC_MAXBLKSIZE for udp and tcp clients? James Pearson
2003-11-26 1:08 ` Greg Banks
2003-11-26 1:40 ` Trond Myklebust
2003-11-26 1:51 ` Greg Banks
2003-11-26 2:00 ` Trond Myklebust
2003-11-26 10:43 ` James Pearson
2003-11-26 22:15 ` Neil Brown
2003-11-27 0:21 ` Greg Banks [this message]
2003-11-27 0:35 ` Neil Brown
2003-11-27 1:33 ` Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 14:20 Lever, Charles
2003-11-27 0:08 ` Greg Banks
2003-11-27 0:53 ` 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=3FC54373.EC448BB1@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=james-p@moving-picture.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.