[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10044.1336643498@redhat.com>
Date: Thu, 10 May 2012 10:51:38 +0100
From: David Howells <dhowells@...hat.com>
To: Dave Chinner <david@...morbit.com>
Cc: dhowells@...hat.com, Andreas Dilger <adilger@...ger.ca>,
linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
linux-ext4@...r.kernel.org, wine-devel@...ehq.org,
kfm-devel@....org, nautilus-list@...me.org,
linux-api@...r.kernel.org, libc-alpha@...rceware.org
Subject: Re: [PATCH 0/6] Extended file stat system call
Dave Chinner <david@...morbit.com> wrote:
> st_blksize - file block size
> st_alloc_blksize - allocation block size/alignment
> st_small_io_size - IO size/alignment that avoids
> filesystem/page cache RMW
> st_preferred_io_size - preferred IO size for general
> usage.
> st_large_io_size - IO size/alignment for high
> bandwidth sequential IO
What is st_blksize here? Is it directly comparable (if such a thing is
possible) to st_blksize in struct stat? Or does st_preferred_io_size map to
the current st_blksize and your st_blksize map to actual media block size (and
if so, is that the same as st_alloc_blksize? - I presume st_alloc_blksize
must be a multiple of the media block size).
David
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists