From: Alex Tomas <alex.tomas@Sun.COM>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: tytso@mit.edu, adilger@Sun.COM, cmm@us.ibm.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix the soft lockup with multi block allocator.
Date: Fri, 21 Dec 2007 14:21:11 +0300 [thread overview]
Message-ID: <476BA1A7.4080108@sun.com> (raw)
In-Reply-To: <1198235390-18485-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
the patch looks OK
Aneesh Kumar K.V wrote:
> With the multi block allocator when we don't have prealloc space we discard
> the existing preallocaltion data and try to rebuild the buddy cache. While
> discarding the loop through the group specific prealloc list. If we find any
> particular prealloc space being used we mark the space busy. If we are not
> able to find enough free space and if we have any prealloc space busy we loop
> back again. With non preempted kernel this tight loop resulted in watchdog
> timer triggering soft lockup warning.
>
>
> Whe we are allocation the block we search the prealloc list and mark the
> prealloc space used via incrementing pa_count value. One after succesffuly
> allocating the block we need to update the block bitmap and this could
> actually involved a disk io if the bitmap need to read from the disk. This
> actually cause prealloc space to be marked used for quiet a long time. This
> inturn results in the discard logic going on tight loop resulting in watchdog
> timer triggering soft lockup warning.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> fs/ext4/mballoc.c | 12 +++---------
> 1 files changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 844765c..cbc8143 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -3729,7 +3729,7 @@ static int ext4_mb_discard_group_preallocations(struct super_block *sb,
> struct list_head list;
> struct ext4_buddy e4b;
> int err;
> - int busy;
> + int busy = 0;
> int free = 0;
>
> mb_debug("discard preallocation for group %lu\n", group);
> @@ -3754,20 +3754,12 @@ static int ext4_mb_discard_group_preallocations(struct super_block *sb,
> INIT_LIST_HEAD(&list);
>
> repeat:
> - busy = 0;
> ext4_lock_group(sb, group);
> list_for_each_entry_safe(pa, tmp,
> &grp->bb_prealloc_list, pa_group_list) {
> spin_lock(&pa->pa_lock);
> if (atomic_read(&pa->pa_count)) {
> spin_unlock(&pa->pa_lock);
> - /* FIXME!!
> - * It is quiet natural to have the pa being
> - * used on other cpus when we are trying free
> - * space
> - printk(KERN_ERR "uh! busy PA\n");
> - dump_stack();
> - */
> busy = 1;
> continue;
> }
> @@ -3790,7 +3782,9 @@ repeat:
>
> /* if we still need more blocks and some PAs were used, try again */
> if (free < needed && busy) {
> + busy = 0;
> ext4_unlock_group(sb, group);
> + schedule_timeout(HZ);
> goto repeat;
> }
>
next prev parent reply other threads:[~2007-12-21 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 11:09 [PATCH] ext4: Fix the soft lockup with multi block allocator Aneesh Kumar K.V
2007-12-21 11:21 ` Alex Tomas [this message]
2007-12-21 19:10 ` Andreas Dilger
2007-12-24 18:18 ` Alex Tomas
2007-12-24 18:45 ` Andreas Dilger
2008-01-09 12:10 ` Jan Kara
2008-01-09 18:24 ` Aneesh Kumar K.V
2008-01-09 18:44 ` Jan Kara
2008-01-09 19:11 ` Aneesh Kumar K.V
2008-01-09 22:01 ` Mingming Cao
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=476BA1A7.4080108@sun.com \
--to=alex.tomas@sun.com \
--cc=adilger@Sun.COM \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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 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.