From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Valerie Aurora <vaurora@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: Some 64-bit tests
Date: Tue, 9 Jun 2009 01:40:37 +0530 [thread overview]
Message-ID: <20090608201037.GB23723@skywalker> (raw)
In-Reply-To: <18887.1244469441@gamaville.dokosmarshall.org>
Can you try this patch ?
commit 6a910bd1d28be09ba3a0e073bae78285ce057a5f
Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Date: Tue Jun 9 01:38:53 2009 +0530
ext4: Use different normalization method for allocation size.
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index ed8482e..7f2423b 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -633,7 +633,7 @@ static void ext4_mb_mark_free_simple(struct super_block *sb,
BUG_ON(len > EXT4_BLOCKS_PER_GROUP(sb));
- border = 2 << sb->s_blocksize_bits;
+ border = 1 << (sb->s_blocksize_bits + 1);
while (len > 0) {
/* find how many blocks can be covered since this position */
@@ -3063,8 +3063,10 @@ static void ext4_mb_normalize_group_request(struct ext4_allocation_context *ac)
ext4_mb_normalize_request(struct ext4_allocation_context *ac,
struct ext4_allocation_request *ar)
{
- int bsbits, max;
+ int bsbits, i;
+ loff_t max;
ext4_lblk_t end;
+ unsigned int s_mb_stream_request;
loff_t size, orig_size, start_off;
ext4_lblk_t start, orig_start;
struct ext4_inode_info *ei = EXT4_I(ac->ac_inode);
@@ -3090,54 +3092,52 @@ ext4_mb_normalize_request(struct ext4_allocation_context *ac,
}
bsbits = ac->ac_sb->s_blocksize_bits;
+ s_mb_stream_request = EXT4_SB(ac->ac_sb)->s_mb_stream_request;
+ /* make sure this is power of 2 */
+ s_mb_stream_request =
+ roundup_pow_of_two((unsigned long)s_mb_stream_request);
/* first, let's learn actual file size
* given current request is allocated */
size = ac->ac_o_ex.fe_logical + ac->ac_o_ex.fe_len;
- size = size << bsbits;
- if (size < i_size_read(ac->ac_inode))
- size = i_size_read(ac->ac_inode);
-
- /* max size of free chunks */
- max = 2 << bsbits;
+ if (size < (i_size_read(ac->ac_inode) >> bsbits))
+ size = i_size_read(ac->ac_inode) >> bsbits;
+ /*
+ * max free chunk blocks.
+ * (max buddy cache order is (bsbits + 1).
+ */
+ max = 1 << (bsbits + 1);
#define NRL_CHECK_SIZE(req, size, max, chunk_size) \
- (req <= (size) || max <= (chunk_size))
+ (((req <= (size)) && (req <= (chunk_size))) || max <= (chunk_size))
/* first, try to predict filesize */
/* XXX: should this table be tunable? */
start_off = 0;
- if (size <= 16 * 1024) {
- size = 16 * 1024;
- } else if (size <= 32 * 1024) {
- size = 32 * 1024;
- } else if (size <= 64 * 1024) {
- size = 64 * 1024;
- } else if (size <= 128 * 1024) {
- size = 128 * 1024;
- } else if (size <= 256 * 1024) {
- size = 256 * 1024;
- } else if (size <= 512 * 1024) {
- size = 512 * 1024;
- } else if (size <= 1024 * 1024) {
- size = 1024 * 1024;
- } else if (NRL_CHECK_SIZE(size, 4 * 1024 * 1024, max, 2 * 1024)) {
- start_off = ((loff_t)ac->ac_o_ex.fe_logical >>
- (21 - bsbits)) << 21;
- size = 2 * 1024 * 1024;
- } else if (NRL_CHECK_SIZE(size, 8 * 1024 * 1024, max, 4 * 1024)) {
- start_off = ((loff_t)ac->ac_o_ex.fe_logical >>
- (22 - bsbits)) << 22;
- size = 4 * 1024 * 1024;
- } else if (NRL_CHECK_SIZE(ac->ac_o_ex.fe_len,
- (8<<20)>>bsbits, max, 8 * 1024)) {
- start_off = ((loff_t)ac->ac_o_ex.fe_logical >>
- (23 - bsbits)) << 23;
- size = 8 * 1024 * 1024;
- } else {
- start_off = (loff_t)ac->ac_o_ex.fe_logical << bsbits;
- size = ac->ac_o_ex.fe_len << bsbits;
+
+ /*
+ * less than s_mb_stream_request is using locality group
+ * preallocation
+ */
+ if (size <= s_mb_stream_request)
+ size = s_mb_stream_request;
+ i = 4;
+ while (1) {
+ /*
+ * if (size <= 4 * s_mb_stream ||
+ * max <= 2 * s_mb_stream ) size = 2 * s_mb_stream
+ */
+ if (NRL_CHECK_SIZE(size, i * s_mb_stream_request,
+ max, ((i * s_mb_stream_request) >> 1))) {
+ /* number of blocks */
+ size = (i * s_mb_stream_request) >> 1;
+ size = size << bsbits;
+ start_off = (loff_t)ac->ac_o_ex.fe_logical & ~(size - 1);
+ break;
+ }
+ i = i << 1;
}
+
orig_size = size = size >> bsbits;
orig_start = start = start_off >> bsbits;
next prev parent reply other threads:[~2009-06-08 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 13:57 Some 64-bit tests Nick Dokos
2009-06-08 19:00 ` Valerie Aurora
2009-06-08 20:10 ` Aneesh Kumar K.V [this message]
2009-06-09 3:13 ` Nick Dokos
2009-06-10 18:13 ` Theodore Tso
2009-06-11 5:50 ` Aneesh Kumar K.V
2009-06-13 4:24 ` Theodore Tso
2009-06-18 21:11 ` Theodore Tso
2009-06-19 11:34 ` 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=20090608201037.GB23723@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
--cc=tytso@mit.edu \
--cc=vaurora@redhat.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 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.