From: Benjamin LaHaise <bcrl@kvack.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4: indirect block allocations not sequential in 3.4.67 and 3.11.7
Date: Wed, 15 Jan 2014 16:56:13 -0500 [thread overview]
Message-ID: <20140115215613.GD12751@kvack.org> (raw)
In-Reply-To: <20140115203205.GA12751@kvack.org>
On Wed, Jan 15, 2014 at 03:32:05PM -0500, Benjamin LaHaise wrote:
> I tried a few tests setting goal to different things, but evidently I'm
> not managing to convince mballoc to put the file's data close to my goal
> block, something in that mess of complicated logic is making it ignore
> the goal value I'm passing in.
It appears that ext4_new_meta_blocks() essentially ignores the goal block
specified for metadata blocks. If I hack around things and pass in the
EXT4_MB_HINT_TRY_GOAL flag where ext4_new_meta_blocks() is called in
ext4_alloc_blocks(), then it will at least try to allocate the block
specified by goal. However, if the block specified by goal is not free,
it ends up allocating blocks many megabytes away, even if one is free
within a few blocks of goal.
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2014-01-15 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 19:28 ext4: indirect block allocations not sequential in 3.4.67 and 3.11.7 Benjamin LaHaise
2014-01-15 20:22 ` Darrick J. Wong
2014-01-15 20:32 ` Benjamin LaHaise
2014-01-15 21:56 ` Benjamin LaHaise [this message]
2014-01-16 3:54 ` Theodore Ts'o
2014-01-16 18:48 ` Benjamin LaHaise
2014-01-16 19:12 ` Theodore Ts'o
2014-01-16 19:30 ` Benjamin LaHaise
2014-01-20 20:52 ` Eric Sandeen
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=20140115215613.GD12751@kvack.org \
--to=bcrl@kvack.org \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
/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).