From: Nathan Scott <nathans@sgi.com>
To: L A Walsh <law@tlinx.org>
Cc: Linux-Xfs <linux-xfs@oss.sgi.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: block size in XFS = hard coded constant?
Date: Tue, 1 Oct 2002 07:26:27 +1000 [thread overview]
Message-ID: <20021001072627.A218954@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <NFBBKNPJLGIDJFAHGKMBIEIJCDAA.law@tlinx.org>; from law@tlinx.org on Mon, Sep 30, 2002 at 01:55:38AM -0700
Hello,
On Mon, Sep 30, 2002 at 01:55:38AM -0700, L A Walsh wrote:
> Right -- I know it isn't the filesystem block size.
>
> In this day and age, it seems anachronistic. Given the 10% higher block
> density, not only would it yield higher capacities, but should yield higher
> transfer rates, no?
>
> I know it isn't a simple constant switch -- but I wouldn't want to switch
> constants since not all disks should be constrained to the same block size.
>
I have some code which implements an initial version of >512 byte sector
sizes for the XFS data device - I was just chatting about this with Steve
today. Initial benchmarking results seem to suggest that it does indeed
perform slightly better. Support for this will likely be making its way
into XFS in the future, but not right away.
cheers.
--
Nathan
prev parent reply other threads:[~2002-09-30 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1033336748.1088.4.camel@laptop.americas.sgi.com>
[not found] ` <NFBBKNPJLGIDJFAHGKMBIEIJCDAA.law@tlinx.org>
2002-09-30 12:07 ` block size in XFS = hard coded constant? Olaf Frączyk
2002-09-30 21:26 ` Nathan Scott [this message]
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=20021001072627.A218954@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=law@tlinx.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).