From: Oleg Drokin <green@namesys.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Hans Reiser <reiser@namesys.com>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] comments on st_blksize and f_bsize for 2.5
Date: Mon, 24 Feb 2003 14:10:36 +0300 [thread overview]
Message-ID: <20030224141036.A11501@namesys.com> (raw)
In-Reply-To: <20030224102009.GB14024@win.tue.nl>
Hello!
On Mon, Feb 24, 2003 at 11:20:09AM +0100, Andries Brouwer wrote:
> The trivial part is st_blksize: all agree.
> Quoting the man page:
> The value st_blksize gives the "preferred" blocksize
> for efficient file system I/O. (Writing to a file in
> smaller chunks may cause an inefficient read-modify-rewrite.)
> The nontrivial part is f_bsize. As far as I can see
> BSD and SYSV and SUS all differ. And there are the use
> in struct statfs and the use in struct statvfs that are
> nonequivalent.
> Maybe BSD f_iosize, f_bsize in statfs corresponds to
> SYSV f_bsize, f_frsize in statfs. Linux is again a
> bit different.
Traditionally in Linux f_bsize in struct statfs is used as FS block size.
(e.g. df calculates fs capacity by multiplying amount of blocks on
fs by f_bsize).
Actually, this is the only field in struct statfs that holds any data regarding
fs blocksize. (well, some arches have f_frsize, but it is marked as unused).
Bye,
Oleg
next prev parent reply other threads:[~2003-02-24 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 17:25 [PATCH] comments on st_blksize and f_bsize for 2.5 Hans Reiser
2003-02-24 10:20 ` Andries Brouwer
2003-02-24 11:10 ` Oleg Drokin [this message]
2003-02-24 12:56 ` Hans Reiser
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=20030224141036.A11501@namesys.com \
--to=green@namesys.com \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=torvalds@transmeta.com \
/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