linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Daniel Phillips <phillips@bonn-fries.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org (Linux Kernel List),
	reiserfs-list@namesys.com (ReiserFS List),
	mason@suse.com (Chris Mason),
	NikitaDanilov@Yahoo.COM (Nikita Danilov),
	tmv5@home.com (Tom Vier)
Subject: Re: 2.4.7-ac4 disk thrashing
Date: Wed, 8 Aug 2001 18:03:36 +0200	[thread overview]
Message-ID: <20010808161334Z270517-28344+3065@vger.kernel.org> (raw)
In-Reply-To: <E15UR2B-00051d-00@the-village.bc.nu> <01080817411402.00351@starship>
In-Reply-To: <01080817411402.00351@starship>

Am Mittwoch, 8. August 2001 17:41 schrieb Daniel Phillips:
> On Wednesday 08 August 2001 12:57, Alan Cox wrote:
> > > Could it be that the ReiserFS cleanups in ac4 do harm?
> > > http://marc.theaimsgroup.com/?l=3Dreiserfs&m=3D99683332027428&w=3D2
> >
> > I suspect the use once patch is the more relevant one.
>
> Two things to check:
>
>   - Linus found a bug in balance_dirty_state yesterday.  Is the
>     fix applied?

No, I'll try.

>   - The original use-once patch tends to leave a referenced pages
>     on the inactive_dirty queue longer, not in itself a problem,
>     but can expose other problems.  The previously posted patch
>     below fixes that, is it applied?
>
> To apply (with use-once already applied):

Yes, it was with -ac9.

But it wasn't much different from ac6/7/8 without it. All nearly "equally 
bad". The disk steps like mad compared against 2.4.7-ac1 and ac-3. I can 
"hear" it and the whole system "feels" slow.
2.4.7-ac1 + transaction-tracking-2 (Chris) + use-once-pages 
(Daniel) + 2.4.7-unlink-truncate-rename-rmdir.dif (Nikita) is the best Linux 
I've ever run.

I did several (~10 times) dbench-1.1 (should I retry with dbench-1.2?) and 
all gave nearly same results.

ac-1, ac3 + fixes			GREAT
ac5, ac6, ac7, ac8, ac9 + fixes	BAD

Thanks,
	Dieter

>   cd /usr/src/your.2.4.7.source.tree
>   patch -p0 <this.patch
>
> --- ../2.4.7.clean/mm/filemap.c	Sat Aug  4 14:27:16 2001
> +++ ./mm/filemap.c	Sat Aug  4 23:41:00 2001
> @@ -979,9 +979,13 @@
>
>  static inline void check_used_once (struct page *page)
>  {
> -	if (!page->age) {
> -		page->age = PAGE_AGE_START;
> -		ClearPageReferenced(page);
> +	if (!PageActive(page)) {
> +		if (page->age)
> +			activate_page(page);
> +		else {
> +			page->age = PAGE_AGE_START;
> +			ClearPageReferenced(page);
> +		}
>  	}
>  }

  reply	other threads:[~2001-08-08 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  6:38 2.4.7-ac4 disk thrashing Dieter Nützel
2001-08-08 10:57 ` Alan Cox
2001-08-08 15:41   ` Daniel Phillips
2001-08-08 16:03     ` Dieter Nützel [this message]
2001-08-13  6:24     ` 2.4.7-ac4 disk thrashing (SOLVED?) Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2001-08-04 15:38 2.4.7-ac4 disk thrashing Tom Vier
2001-08-04 23:04 ` Matthew Gardiner
2001-08-05  0:55   ` Tom Vier

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=20010808161334Z270517-28344+3065@vger.kernel.org \
    --to=dieter.nuetzel@hamburg.de \
    --cc=NikitaDanilov@Yahoo.COM \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=phillips@bonn-fries.net \
    --cc=reiserfs-list@namesys.com \
    --cc=tmv5@home.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).