lkml.org 
[lkml]   [2003]   [Sep]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: effect of nfs blocksize on I/O ?
From
>>>>> " " == 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.110 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site