From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC] mballoc patches
Date: Tue, 21 Aug 2007 16:00:43 -0500 [thread overview]
Message-ID: <46CB527B.5090300@redhat.com> (raw)
In-Reply-To: <46C08902.7020709@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
>
>
> I am attaching below the PATCH 2/4 in .gz format. The uncompressed one
> got dropped by the list.
>
> -aneesh
hmm makes it hard to comment in-line though :) So basing this on the
patch currently in the git repo.
+/*
+ * default stripe size = 1MB
+ */
+#define MB_DEFAULT_STRIPE 256
Units? Doesn't seem to matter anyway as it's never referenced.
+ /* tunables */
+ unsigned long s_mb_factor;
+ unsigned long s_stripe;
+ unsigned long s_mb_small_req;
+ unsigned long s_mb_large_req;
+ unsigned long s_mb_max_to_scan;
+ unsigned long s_mb_min_to_scan;
could we get some comments here as to what these are, and what units?
Same is true many places... for example
+static int mb_find_extent(struct ext4_buddy *e3b, int order, int block,
+ int needed, struct ext4_free_extent *ex)
how many "what" are needed?
And perhaps an addition of the new mount options to
Documentation/fs/ext4.txt would be good.
+#define EXT4_MB_BITMAP(e3b) ((e3b)->bd_bitmap)
+#define EXT4_MB_BUDDY(e3b) ((e3b)->bd_buddy)
For the sake of consistency should these (and others) be e4b?
Also there are a *lot* of BUGs and BUG_ONs added in this patch... are
none of these recoverable?
Thanks,
-Eric
next prev parent reply other threads:[~2007-08-21 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 10:22 [RFC] mballoc patches Aneesh Kumar K.V
2007-08-13 10:22 ` [PATCH 1/4] Add some new function for searching extent tree Aneesh Kumar K.V
[not found] ` <1187000553923-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
2007-08-13 10:22 ` [PATCH 3/4] This is the equivalent of ext3-mballoc3-sles10.patch Aneesh Kumar K.V
2007-08-13 10:22 ` [PATCH 4/4] Fixes to make it build and run Aneesh Kumar K.V
2007-08-13 16:38 ` [RFC] mballoc patches Aneesh Kumar K.V
2007-08-21 21:00 ` Eric Sandeen [this message]
2007-09-10 12:29 ` Alex Tomas
2007-09-10 14:35 ` 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=46CB527B.5090300@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.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).