From: Stephan von Krawczynski <skraw@ithnet.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, riel@conectiva.com.br
Subject: Re: 2.4.8/2.4.9 problem
Date: Thu, 23 Aug 2001 17:39:20 +0200 [thread overview]
Message-ID: <20010823173920.652a175a.skraw@ithnet.com> (raw)
In-Reply-To: <20010823144024Z16183-32384+397@humbolt.nl.linux.org>
In-Reply-To: <200108171310.PAA26032@lambik.cc.kuleuven.ac.be> <20010820211403Z16263-32383+585@humbolt.nl.linux.org> <20010823140444.A14798@spylog.ru> <20010823144024Z16183-32384+397@humbolt.nl.linux.org>
On Thu, 23 Aug 2001 16:46:54 +0200
Daniel Phillips <phillips@bonn-fries.net> wrote:
> Marcelo already posted a patch to fix this problem (bounce buffer allocation).
> Look under subject "Re: With Daniel Phillips Patch (was: aic7xxx with 2.4.9 on
> 7899P)" with a correction in his next post.
Aehm, Daniel, just to inform you: Marcelos patch does not solve the problem. I just proofed it here. Is completely the same with or without patch.
I tried another thing which might be interesting. I think your opinion is that page_launder gives you free memory if available when the system runs short. But it does not. I tried the following:
DEF_PRIORITY in vmscan.c set to 0. This should come out as page_launder doing the complete pagelist over in search of free pages. And guess what: it does not find enough to keep the system running. In other words: at least the search strategy in page_launder is broken, too. I can see 500 Megs of Inact_dirty mem, but page_launder cannot find enough clean ones to keep a simple filecopy running.
Any ideas left.
Regards,
Stephan
next prev parent reply other threads:[~2001-08-23 15:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 13:10 2.4.8/2.4.9 VM problems Frank Dekervel
2001-08-19 21:00 ` Daniel Phillips
2001-08-19 21:13 ` 2.4.8/2.4.9 problem Andrey Nekrasov
2001-08-20 21:20 ` Daniel Phillips
2001-08-23 10:04 ` Andrey Nekrasov
2001-08-23 14:46 ` Daniel Phillips
2001-08-23 15:39 ` Stephan von Krawczynski [this message]
2001-08-23 18:05 ` Daniel Phillips
2001-08-20 15:40 ` 2.4.8/2.4.9 VM problems Mike Galbraith
2001-08-20 17:10 ` Daniel Phillips
2001-08-20 19:14 ` Mike Galbraith
2001-08-20 20:34 ` Daniel Phillips
2001-08-20 19:12 ` Marcelo Tosatti
2001-08-20 21:40 ` Daniel Phillips
2001-08-20 20:08 ` Marcelo Tosatti
2001-08-20 20:16 ` Marcelo Tosatti
2001-08-20 22:54 ` Daniel Phillips
2001-08-20 21:50 ` Marcelo Tosatti
2001-08-20 23:29 ` Daniel Phillips
2001-08-20 22:05 ` Marcelo Tosatti
2001-08-20 23:54 ` Daniel Phillips
2001-08-21 1:55 ` Rik van Riel
2001-08-21 3:51 ` Daniel Phillips
2001-08-21 3:58 ` Rik van Riel
2001-08-21 4:11 ` Daniel Phillips
2001-08-21 4:08 ` Rik van Riel
2001-08-20 21:44 ` Rik van Riel
2001-08-20 22:47 ` Daniel Phillips
2001-08-21 4:52 ` Mike Galbraith
2001-08-21 5:14 ` Rik van Riel
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=20010823173920.652a175a.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
/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