From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [patch] Fix xfs_iunpin() sets I_DIRTY_SYNC after clear_inode().
Date: Fri, 13 Oct 2006 21:17:01 +0900 [thread overview]
Message-ID: <452F83BD.8050501@ah.jp.nec.com> (raw)
In-Reply-To: <20061013014651.GC19345@melbourne.sgi.com>
Hi David,
David Chinner wrote:
>> Block I/O performance degradation was very serious.
>
> That was unexpected. :/
>
>> Now, I am trying to ease the degradation.
>> Do you have any idea for resolving the degradation?
>
> Did you see a degradation with your original fix? I suspect
> not.
No, I don't see any degradation with my patch.
But my patch is not perfect.
Because xfs_log_force() don't guarantee to write the log in run time.
>
> Can you test this patch (on top of the last patch I sent)
> and see if it fixes the degradation?
I tried your patch, but it seems degradation was not resolved.
procs -----------memory---------- ---swap-- -----io---- -system-- -----cpu------
r b swpd free buff cache si so bi bo in cs us sy id wa st
1 0 0 15585968 21856 151696 0 0 73 273 258 298 1 3 94 2 0
0 0 0 15585968 21856 151840 0 0 0 2270 2156 2693 0 2 98 0 0
1 0 0 15585744 21856 151920 0 0 0 2362 2161 2797 0 2 98 0 0
0 0 0 15585408 21856 151824 0 0 0 2291 2156 2732 0 2 98 0 0
0 0 0 15584848 21856 152288 0 0 0 2300 2156 2765 0 2 98 0 0
2 0 0 15584848 21856 151952 0 0 0 2346 2161 2809 0 2 98 0 0
Ummmm, I think schedule() was called many times by wait_event().
Best Regards,
--
Takenori Nagano, NEC
t-nagano@ah.jp.nec.com
next prev parent reply other threads:[~2006-10-13 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 9:20 [patch] Fix xfs_iunpin() sets I_DIRTY_SYNC after clear_inode() Takenori Nagano
2006-10-06 3:26 ` David Chinner
2006-10-11 6:43 ` David Chinner
2006-10-12 12:20 ` Takenori Nagano
2006-10-13 1:46 ` David Chinner
2006-10-13 8:06 ` Timothy Shimmin
2006-10-13 12:17 ` Takenori Nagano [this message]
2006-10-17 2:02 ` David Chinner
2006-10-18 2:33 ` David Chinner
2006-10-18 9:07 ` David Chinner
2006-10-19 2:23 ` Takenori Nagano
2006-10-19 4:58 ` David Chinner
2006-10-20 4:25 ` Takenori Nagano
2006-10-23 6:53 ` Takenori Nagano
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=452F83BD.8050501@ah.jp.nec.com \
--to=t-nagano@ah.jp.nec.com \
--cc=dgc@sgi.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