From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
To: "David Chinner" <dgc@sgi.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Fengguang Wu" <wfg@mail.ustc.edu.cn>,
"Maxim Levitsky" <maximlevitsky@gmail.com>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: writeout stalls in current -git
Date: Mon, 5 Nov 2007 19:27:16 +0100 [thread overview]
Message-ID: <64bb37e0711051027v49869699s9593ea54713b15ff@mail.gmail.com> (raw)
In-Reply-To: <20071105014510.GU66820511@sgi.com>
On 11/5/07, David Chinner <dgc@sgi.com> wrote:
> Ok, so it's probably a side effect of the writeback changes.
>
> Attached are two patches (two because one was in a separate patchset as
> a standalone change) that should prevent async writeback from blocking
> on locked inode cluster buffers. Apply the xfs-factor-inotobp patch first.
> Can you see if this fixes the problem?
Now testing v2.6.24-rc1-650-gb55d1b1+ the fix for the missapplied raid5-patch
Applying your two patches ontop of that does not fix the stalls.
vmstat 10 output from unmerging (uninstalling) a kernel:
1 0 0 3512188 332 192644 0 0 185 12 368 735 10 3 85 1
-> emerge starts to remove the kernel source files
3 0 0 3506624 332 192836 0 0 15 9825 2458 8307 7 12 81 0
0 0 0 3507212 332 192836 0 0 0 554 630 1233 0 1 99 0
0 0 0 3507292 332 192836 0 0 0 537 580 1328 0 1 99 0
0 0 0 3507168 332 192836 0 0 0 633 626 1380 0 1 99 0
0 0 0 3507116 332 192836 0 0 0 1510 768 2030 1 2 97 0
0 0 0 3507596 332 192836 0 0 0 524 540 1544 0 0 99 0
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 0 3507540 332 192836 0 0 0 489 551 1293 0 0 99 0
0 0 0 3507528 332 192836 0 0 0 527 510 1432 1 1 99 0
0 0 0 3508052 332 192840 0 0 0 2088 910 2964 2 3 95 0
0 0 0 3507888 332 192840 0 0 0 442 565 1383 1 1 99 0
0 0 0 3508704 332 192840 0 0 0 497 529 1479 0 0 99 0
0 0 0 3508704 332 192840 0 0 0 594 595 1458 0 0 99 0
0 0 0 3511492 332 192840 0 0 0 2381 1028 2941 2 3 95 0
0 0 0 3510684 332 192840 0 0 0 699 600 1390 0 0 99 0
0 0 0 3511636 332 192840 0 0 0 741 661 1641 0 0 100 0
0 0 0 3524020 332 192840 0 0 0 2452 1080 3910 2 3 95 0
0 0 0 3524040 332 192844 0 0 0 530 617 1297 0 0 99 0
0 0 0 3524128 332 192844 0 0 0 812 674 1667 0 1 99 0
0 0 0 3527000 332 193672 0 0 339 721 754 1681 3 2 93 1
-> emerge is finished, no dirty or writeback data in /proc/meminfo
0 0 0 3571056 332 194768 0 0 111 639 632 1344 0 1 99 0
0 0 0 3571260 332 194768 0 0 0 757 688 1405 1 0 99 0
0 0 0 3571156 332 194768 0 0 0 753 641 1361 0 0 99 0
0 0 0 3571404 332 194768 0 0 0 766 653 1389 0 0 99 0
1 0 0 3571136 332 194768 0 0 6 764 669 1488 0 0 99 0
0 0 0 3571668 332 194824 0 0 0 764 657 1482 0 0 99 0
0 0 0 3571848 332 194824 0 0 0 673 659 1406 0 0 99 0
0 0 0 3571908 332 195052 0 0 22 753 638 1500 0 1 99 0
0 0 0 3573052 332 195052 0 0 0 765 631 1482 0 1 99 0
0 0 0 3574144 332 195052 0 0 0 771 640 1497 0 0 99 0
0 0 0 3573468 332 195052 0 0 0 458 485 1251 0 0 99 0
0 0 0 3574184 332 195052 0 0 0 427 474 1192 0 0 100 0
0 0 0 3575092 332 195052 0 0 0 461 482 1235 0 0 99 0
0 0 0 3576368 332 195056 0 0 0 582 556 1310 0 0 99 0
0 0 0 3579300 332 195056 0 0 0 695 571 1402 0 0 99 0
0 0 0 3580376 332 195056 0 0 0 417 568 906 0 0 99 0
0 0 0 3581212 332 195056 0 0 0 421 559 977 0 1 99 0
0 0 0 3583780 332 195060 0 0 0 494 555 1080 0 1 99 0
0 0 0 3584352 332 195060 0 0 0 99 347 559 0 0 99 0
0 0 0 3585232 332 195060 0 0 0 11 301 621 0 0 99 0
-> disks go idle.
So these patches do not seem to be the source of these excessive disk writes...
Torsten
next prev parent reply other threads:[~2007-11-05 18:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710220822.52370.maximlevitsky@gmail.com>
[not found] ` <200710221258.11384.maximlevitsky@gmail.com>
[not found] ` <393051953.24752@ustc.edu.cn>
[not found] ` <200710221421.21439.maximlevitsky@gmail.com>
[not found] ` <393126119.26275@ustc.edu.cn>
[not found] ` <1193134027.7406.1.camel@twins>
[not found] ` <20071023115620.GA5678@mail.ustc.edu.cn>
2007-10-23 11:56 ` [PATCH] reiserfs: don't drop PG_dirty when releasing sub-page-sized dirty file Fengguang Wu
2007-10-23 14:10 ` Chris Mason
[not found] ` <20071023144014.GA6174@mail.ustc.edu.cn>
2007-10-23 14:40 ` Fengguang Wu
2007-10-23 14:40 ` Fengguang Wu
2007-10-23 11:56 ` Fengguang Wu
[not found] ` <393056632.00561@ustc.edu.cn>
[not found] ` <200710221505.35397.maximlevitsky@gmail.com>
[not found] ` <20071022131045.GA5357@mail.ustc.edu.cn>
[not found] ` <393060478.03650@ustc.edu.cn>
[not found] ` <64bb37e0710310822r5ca6b793p8fd97db2f72a8655@mail.gmail.com>
[not found] ` <393903856.06449@ustc.edu.cn>
[not found] ` <64bb37e0711011120i63cdfe3ci18995d57b6649a8@mail.gmail.com>
[not found] ` <E1Inljm-0002DW-CL@localhost>
2007-11-02 1:54 ` writeout stalls in current -git Fengguang Wu
2007-11-02 1:54 ` Fengguang Wu
2007-11-02 7:42 ` Torsten Kaiser
[not found] ` <E1InrKN-0000MK-G5@localhost>
2007-11-02 7:52 ` Fengguang Wu
2007-11-02 7:52 ` Fengguang Wu
2007-11-02 17:47 ` Torsten Kaiser
[not found] ` <64bb37e0711011200n228e708eg255640388f83da22@mail.gmail.com>
[not found] ` <E1InmAI-0003ME-2i@localhost>
2007-11-02 2:21 ` Fengguang Wu
2007-11-02 2:21 ` Fengguang Wu
2007-11-02 7:50 ` Torsten Kaiser
2007-11-02 10:15 ` Peter Zijlstra
[not found] ` <E1IntqD-0001dK-OE@localhost>
2007-11-02 10:33 ` Fengguang Wu
2007-11-02 10:33 ` Fengguang Wu
2007-11-05 23:57 ` Andrew Morton
2007-11-06 10:20 ` Peter Zijlstra
2007-11-02 19:22 ` Torsten Kaiser
2007-11-02 20:43 ` David Chinner
2007-11-02 21:02 ` Torsten Kaiser
2007-11-04 11:19 ` Torsten Kaiser
2007-11-05 1:45 ` David Chinner
2007-11-05 7:01 ` Torsten Kaiser
2007-11-05 18:27 ` Torsten Kaiser [this message]
2007-11-06 4:25 ` David Chinner
2007-11-06 7:10 ` Torsten Kaiser
2007-11-06 19:01 ` Peter Zijlstra
2007-11-06 20:26 ` Torsten Kaiser
[not found] ` <E1IpKZ4-0004je-Lb@localhost>
2007-11-06 9:17 ` Fengguang Wu
2007-11-06 9:17 ` Fengguang Wu
2007-11-06 21:53 ` Torsten Kaiser
2007-11-06 23:31 ` David Chinner
2007-11-07 2:13 ` David Chinner
2007-11-07 7:15 ` Torsten Kaiser
2007-11-08 0:38 ` David Chinner
2007-11-20 13:16 ` Damien Wyart
2007-11-20 21:09 ` David Chinner
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=64bb37e0711051027v49869699s9593ea54713b15ff@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=peterz@infradead.org \
--cc=wfg@mail.ustc.edu.cn \
--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;
as well as URLs for NNTP newsgroup(s).