From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix small file fragmentation
Date: Sat, 16 Aug 2008 16:13:04 +0530 [thread overview]
Message-ID: <20080816104304.GF6423@skywalker> (raw)
In-Reply-To: <20080815175243.GD6511@skywalker>
On Fri, Aug 15, 2008 at 11:22:43PM +0530, Aneesh Kumar K.V wrote:
> commit 6ad9d25595aea8efa0d45c0a2dd28b4a415e34e6
> Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date: Fri Aug 15 23:19:15 2008 +0530
>
> move the dirty inodes to the end of the list
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 1afcb11..650b021 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4258,7 +4258,8 @@ ext4_mb_discard_lg_preallocations(struct super_block *sb,
>
> static void ext4_mb_add_n_trim(struct ext4_allocation_context *ac)
> {
> - int order, added = 0, lg_prealloc_count = 1;
> + int order, lg_prealloc_count = 1;
> + bool added = 0;
> struct super_block *sb = ac->ac_sb;
> struct ext4_locality_group *lg = ac->ac_lg;
> struct ext4_prealloc_space *tmp_pa, *pa = ac->ac_pa;
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 25adfc3..95eee62 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -163,7 +163,7 @@ void __mark_inode_dirty(struct inode *inode, int flags)
> */
> if (!was_dirty) {
> inode->dirtied_when = jiffies;
> - list_move(&inode->i_list, &sb->s_dirty);
> + list_move_tail(&inode->i_list, &sb->s_dirty);
> }
> }
> out:
> @@ -208,7 +208,7 @@ static void redirty_tail(struct inode *inode)
> */
> static void requeue_io(struct inode *inode)
> {
> - list_move(&inode->i_list, &inode->i_sb->s_more_io);
> + list_move_tail(&inode->i_list, &inode->i_sb->s_more_io);
> }
>
> static void inode_sync_complete(struct inode *inode)
The patch is not really useful and is also wrong. Verifying the results
again I found that patch didn't make any difference. We actually read
from the s_io list from the tail not from the head (generic_sync_sb_inodes)
That means inodes are already added in the order they are dirtied.
-aneesh
prev parent reply other threads:[~2008-08-16 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 17:44 [PATCH] ext4: Fix small file fragmentation Aneesh Kumar K.V
2008-08-14 22:16 ` Mingming Cao
[not found] ` <20080814231816.GA13048@mit.edu>
2008-08-15 13:38 ` Theodore Tso
2008-08-15 16:31 ` Aneesh Kumar K.V
2008-08-15 16:33 ` Aneesh Kumar K.V
2008-08-15 17:52 ` Aneesh Kumar K.V
2008-08-15 18:07 ` Aneesh Kumar K.V
2008-08-15 20:05 ` Theodore Tso
2008-08-16 4:43 ` Aneesh Kumar K.V
2008-08-16 10:43 ` Aneesh Kumar K.V [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=20080816104304.GF6423@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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