From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frank Cusack <fcusack@fcusack.com>
Cc: torvalds@osld.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: effect of nfs blocksize on I/O ?
Date: Mon, 29 Sep 2003 01:27:51 -0700 [thread overview]
Message-ID: <16247.60679.415937.295532@charged.uio.no> (raw)
In-Reply-To: <20030929005250.A9110@google.com>
>>>>> " " == Frank Cusack <fcusack@fcusack.com> writes:
>> OTOH, bsize is of informational interest to programs that wish
>> to optimize I/O throughput by grouping their data into
>> appropriately sized records.
> So then isn't the optimal record size 8192 for r/wsize=8192?
> Since the data is going to be grouped into 8192-byte reads and
> writes over the wire, shouldn't bsize match that? Why should I
> make 16x 512-byte write() syscalls (if "optimal" I/O size is
> bsize=512) instead of 1x 8192-byte syscall?
Yes. It is already on my list of bugs.
We basically need to feed 'wtpref' (a.k.a. 'wsize') into the f_bsize,
and 'wtmult' into f_frsize.
OTOH, the s_blocksize (and inode->i_blkbits) might well want to stay
with wtmult.
Cheers,
Trond
next prev parent reply other threads:[~2003-09-29 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 6:42 Frank Cusack
2003-09-29 7:19 ` Trond Myklebust
2003-09-29 7:52 ` Frank Cusack
2003-09-29 8:27 ` Trond Myklebust [this message]
2003-09-30 5:23 ` Frank Cusack
2003-09-30 6:04 ` 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=16247.60679.415937.295532@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osld.org \
/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®