From: Andreas Dilger <adilger@dilger.ca>
To: Teng-Feng Yang <shinrairis@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: EXT4 data block allocation alignment
Date: Wed, 11 Jun 2014 11:58:17 -0600 [thread overview]
Message-ID: <4B4CADE4-6780-439B-AD5E-4DDCA9EB4EA5@dilger.ca> (raw)
In-Reply-To: <CAKTMprNG5GzBQ1wmPhvCWzr3OKcsj8HCQ4f-mez_bSvw5D9f4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Jun 11, 2014, at 5:44 AM, Teng-Feng Yang <shinrairis@gmail.com> wrote:
> Recently I have been working on a small project which requires data
> blocks of each file to be aligned to 512KB/1MB boundary for
> performance reason. As far as I know, this can be accomplished by
> setting the stripe unit on XFS or enabling the "bigalloc" feature on
> EXT4. However, the "bigalloc" feature has not yet been stated to be
> stable in the latest release. So, this makes me wondering if I can
> achieve this block allocation alignment by setting the stride-size on
> EXT4. The document of mke2fs only says that this value may be used by
> the block allocator, so I am not quite sure what it can offer for me
> in this case.
In fact, 1MB alignment is already the default behaviour for ext4
extent-mapped allocations, though it isn't enforced for small files.
It is possible to specify the alignment with "-E stripe_width={blocks}"
(blocks=256 for 1MB and =128 for 512KB, assuming 4KB blocksize).
It might be possible to implement this alignment as required instead
of optional for data blocks, but that would need a change to the code.
It would still be more space efficient than bigalloc, since bigalloc
will allocate a full 512KB for each metadata block or directory.
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2014-06-11 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 11:44 EXT4 data block allocation alignment Teng-Feng Yang
2014-06-11 13:03 ` Lukáš Czerner
2014-06-11 17:58 ` Andreas Dilger [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=4B4CADE4-6780-439B-AD5E-4DDCA9EB4EA5@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=shinrairis@gmail.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