- Subject: Re: [PATCH 0/6] Extended file stat system call
- From: Steve French <smfrench@xxxxxxxxx>
- Date: Fri, 27 Apr 2012 19:54:12 -0500
- Cc: Andreas Dilger <adilger@xxxxxxxxxxxxx>, David Howells <dhowells@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx, samba-technical@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, wine-devel@xxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, libc-alpha@xxxxxxxxxxxxxx
- In-reply-to: <20120428003833.GH9541@dastard>
- References: <20120419140558.17272.74360.stgit@warthog.procyon.org.uk> <20120427010610.GE9541@dastard> <ED5B8F1B-6C99-4516-85FA-A767E94B635F@dilger.ca> <20120428003833.GH9541@dastard>
On Fri, Apr 27, 2012 at 7:38 PM, Dave Chinner <david@xxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]