From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@sun.com>, Alex Tomas <bzzz@sun.com>
Cc: linux-ext4@vger.kernel.org
Subject: Questions about mballoc's stream allocation
Date: Fri, 07 Aug 2009 09:07:53 -0400 [thread overview]
Message-ID: <E1MZPAn-0001Y0-TQ@closure.thunk.org> (raw)
I've got two questions about mballoc's stream allocation.
First of all, in ext4_mb_regular_allocator(), I'm 99% sure this is a
bug:
/* if stream allocation is enabled, use global goal */
size = ac->ac_o_ex.fe_logical + ac->ac_o_ex.fe_len;
isize = i_size_read(ac->ac_inode) >> bsbits;
if (size < isize)
size = isize;
if (size < sbi->s_mb_stream_request &&
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(ac->ac_flags & EXT4_MB_HINT_DATA)) {
/* TBD: may be hot point */
spin_lock(&sbi->s_md_lock);
ac->ac_g_ex.fe_group = sbi->s_mb_last_group;
ac->ac_g_ex.fe_start = sbi->s_mb_last_start;
spin_unlock(&sbi->s_md_lock);
}
Shouldn't that be ">=", not "<". We want to use the values saved in
sbi->s_mb_last_{group,start} only if we are doing a stream allocation,
which would be true only if the file is *larger* than
s_mb_stream_request, no?
The second question I have is with regards to ext4_mb_use_best_found(),
we set sbi->s_mb_last_{group,start} on any data allocation; shouldn't we
only be setting those values only if we were doing a stream allocation
in the first place?
Otherwise, any kind of allocation will end up moving the global goal
block for stream allocations; even if it is a small allocation in the
middle of some block group caused by the flag EXT4_MB_HINT_NO_PREALLOC
being set.
Am I missing anything?
- Ted
next reply other threads:[~2009-08-07 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 13:07 Theodore Ts'o [this message]
2009-08-08 7:51 ` Questions about mballoc's stream allocation Andreas Dilger
2009-08-08 22:52 ` [PATCH,RFC 1/2] ext4: Fix bugs in mballoc's stream allocation mode Theodore Ts'o
2009-08-08 22:52 ` [PATCH,RFC 2/2] ext4: Avoid group preallocation for closed files Theodore Ts'o
2009-08-11 15:39 ` Questions about mballoc's stream allocation Aneesh Kumar K.V
2009-08-11 17:37 ` Aneesh Kumar K.V
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=E1MZPAn-0001Y0-TQ@closure.thunk.org \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=bzzz@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.