Re: [PATCH 0/6] Extended file stat system call
From: Steve French <smfrench@gmail.com>
Date: 2012-04-28 00:54:12
Also in:
linux-api, linux-cifs, linux-fsdevel, linux-nfs
Possibly related (same subject, not in this thread)
- 2012-05-10 · Re: [PATCH 0/6] Extended file stat system call · David Howells <dhowells@redhat.com>
- 2012-04-28 · Re: [PATCH 0/6] Extended file stat system call · Dave Chinner <david@fromorbit.com>
- 2012-04-27 · Re: [PATCH 0/6] Extended file stat system call · Paul Eggert <hidden>
- 2012-04-27 · Re: [PATCH 0/6] Extended file stat system call · Andreas Dilger <hidden>
- 2012-04-27 · Re: [PATCH 0/6] Extended file stat system call · Steve French <hidden>
On Fri, Apr 27, 2012 at 7:38 PM, Dave Chinner [off-list ref] wrote:
preferred minimum IO size (mp->m_readio_log/mp->m_writeio_log)
This discussion about i/o sizes is very interesting. For network file system (at least for SMB2 to all known servers, and for cifs mounts to Samba, but probably for recent NFS), ideal i/o sizes are often well over a megabyte ... but how to indicate that to the application...
That's why I'd prefer specific optimal IO hints - we don't have to overload st_blksize with lots of meanings to pass what is relatively trivial information back to the application. Cheers, Dave. -- Dave Chinner
Yes. -- Thanks, Steve