From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Oliver Tennert <tennert@science-computing.de>
Cc: linux-kernel@vger.kernel.org, kaw@science-computing.de
Subject: Re: NFS client problem and IO blocksize
Date: Wed, 22 Jan 2003 14:41:43 +0100 [thread overview]
Message-ID: <15918.40855.583602.576856@charged.uio.no> (raw)
In-Reply-To: <Pine.GHP.4.02.10301221424430.848-100000@alderaan.science-computing.de>
>>>>> " " == Oliver Tennert <tennert@science-computing.de> writes:
> As you can see, the actual server-side s_blksize is 4k, whereas
> the Linux client takes it to be 512 bytes. An strace output
> confirms that a "cat" of a file actually uses 512 byte IO
> chunks.
I'm taking the value from the NFSv3 'wtmult' attribute, which is
described thus in RFC1813:
wtmult
The suggested multiple for the size of a WRITE
request.
If the AIX NFS server is returning 512 bytes, then that's what
'statfs' returns.
Cheers,
Trond
next prev parent reply other threads:[~2003-01-22 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 10:33 Oliver Tennert
2003-01-22 13:06 ` Trond Myklebust
2003-01-22 13:35 ` Oliver Tennert
2003-01-22 13:41 ` Trond Myklebust [this message]
2003-01-22 14:18 ` Oliver Tennert
2003-01-22 15:32 ` 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=15918.40855.583602.576856@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=kaw@science-computing.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tennert@science-computing.de \
/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
all inboxes | Powered by JetHome®