From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: long hangs when deleting large directories (3.0-rc3)
Date: Tue, 21 Jun 2011 23:22:01 +0200 [thread overview]
Message-ID: <20110621212201.GA1755@x4.trippels.de> (raw)
In-Reply-To: <20110621185701.GB1723@x4.trippels.de>
On 2011.06.21 at 20:57 +0200, Markus Trippelsdorf wrote:
> On 2011.06.21 at 20:24 +0200, Markus Trippelsdorf wrote:
> > On 2011.06.21 at 10:02 +0200, Markus Trippelsdorf wrote:
> > > On 2011.06.21 at 14:25 +1000, Dave Chinner wrote:
> > > > That is, you really need to get a profile of the rm -rf process - or
> > > > whatever is consuming the CPU time - (e.g. via perf or ftrace)
> > > > across the hang to so we can narrow down the potential cause of the
> > > > latency. Speaking of which, latencytop might be helpful in
> > > > identifying where input is getting held up....
> > >
> > > I've recorded a profile with "perf record -g /home/markus/rm_sync"
> > > ~ % cat rm_sync
> > > rm -fr /mnt/tmp/tmp/linux && sync
> >
> > FWIW here are two links to svg time-charts produced by:
> >
> > perf timechart record /home/markus/rm_sync
> >
> > http://trippelsdorf.de/timechart1.svg
> > http://trippelsdorf.de/timechart2.svg
> >
>
> And this is what the mysterious kworker is doing during the sync.
> It's the one consuming most of the CPU time.
>
> 39.96% kworker/3:0 [kernel.kallsyms] 0xffffffff811da9da k [k] xfs_trans_ail_update_bulk
> |
> --- xfs_trans_ail_update_bulk
> xfs_trans_committed_bulk
> xlog_cil_committed
> xlog_state_do_callback
> xlog_state_done_syncing
> xlog_iodone
> xfs_buf_iodone_work
> process_one_work
> worker_thread
> kthread
> kernel_thread_helper
>
The following patch fixes the problem for me.
diff --git a/fs/xfs/linux-2.6/xfs_buf.c b/fs/xfs/linux-2.6/xfs_buf.c
index 5e68099..2f34efd 100644
--- a/fs/xfs/linux-2.6/xfs_buf.c
+++ b/fs/xfs/linux-2.6/xfs_buf.c
@@ -1856,7 +1856,7 @@ xfs_buf_init(void)
goto out;
xfslogd_workqueue = alloc_workqueue("xfslogd",
- WQ_MEM_RECLAIM | WQ_HIGHPRI, 1);
+ WQ_MEM_RECLAIM | WQ_UNBOUND, 1);
if (!xfslogd_workqueue)
goto out_free_buf_zone;
--
Markus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-21 21:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 14:19 long hangs when deleting large directories (3.0-rc3) Markus Trippelsdorf
2011-06-18 14:24 ` Christoph Hellwig
2011-06-18 14:37 ` Markus Trippelsdorf
2011-06-19 8:16 ` Markus Trippelsdorf
2011-06-19 22:24 ` Dave Chinner
2011-06-20 0:54 ` Markus Trippelsdorf
2011-06-20 1:34 ` Dave Chinner
2011-06-20 2:02 ` Markus Trippelsdorf
2011-06-20 2:36 ` Dave Chinner
2011-06-20 6:03 ` Markus Trippelsdorf
2011-06-20 11:13 ` Markus Trippelsdorf
2011-06-20 11:45 ` Michael Monnerie
2011-06-20 12:31 ` Markus Trippelsdorf
2011-06-20 21:16 ` Markus Trippelsdorf
2011-06-21 4:25 ` Dave Chinner
2011-06-21 8:02 ` Markus Trippelsdorf
2011-06-21 18:24 ` Markus Trippelsdorf
2011-06-21 18:57 ` Markus Trippelsdorf
2011-06-21 21:22 ` Markus Trippelsdorf [this message]
2011-06-22 0:04 ` Dave Chinner
2011-06-22 7:06 ` Markus Trippelsdorf
2011-06-22 7:30 ` Dave Chinner
2011-06-22 7:40 ` Markus Trippelsdorf
2011-06-29 4:31 ` Dave Chinner
2011-06-29 6:19 ` Markus Trippelsdorf
2011-06-29 7:24 ` Dave Chinner
2011-06-29 7:41 ` Markus Trippelsdorf
2011-06-29 12:10 ` Dave Chinner
2011-06-29 12:48 ` Markus Trippelsdorf
2011-06-29 15:08 ` Michael Weissenbacher
2011-06-29 23:53 ` Dave Chinner
2011-06-21 10:18 ` Markus Trippelsdorf
2011-06-21 10:40 ` Markus Trippelsdorf
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=20110621212201.GA1755@x4.trippels.de \
--to=markus@trippelsdorf.de \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox