From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: phillips@bonn-fries.net, riel@conectiva.com.br,
jaharkes@cs.cmu.edu, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: page_launder() on 2.4.9/10 issue
Date: Thu, 6 Sep 2001 16:39:09 +0200 [thread overview]
Message-ID: <20010906163909.186b8b46.skraw@ithnet.com> (raw)
In-Reply-To: <594419049.999788509@[10.132.112.53]>
In-Reply-To: <20010906154212.442bdf7b.skraw@ithnet.com> <594419049.999788509@[10.132.112.53]>
On Thu, 06 Sep 2001 15:01:49 +0100 Alex Bligh - linux-kernel
<linux-kernel@alex.org.uk> wrote:
> Yes, but this is because VM system's targets & pressure calcs do not
> take into account fragmentation of the underlying physical memory.
> IE, in theory you could have half your memory free, but
> not be able to allocate a single 8k block. Nothing would cause
> cache, or InactiveDirty stuff to be written.
Which is obviously not the right way to go. I guess we agree in that.
> You yourself proved this, by switching rsize,wsize to 1k and said
> it all worked fine! (unless I misread your email).
Sorry, misunderstanding: I did not touch rsize/wsize. What I do is to lower fs
action by not letting knfsd walk through the subtrees of a mounted fs. This
leads to less allocs/frees by the fs layer which tend to fail and let knfs fail
afterwards.
> [...]
> I think what you want isn't more memory, its less
> fragmented memory.
This is one important part for sure.
> Or an underlying system which can
> cope with fragmentation.
Well, I'd rather prefer the cure than the dope :-)
Regards, Stephan
next prev parent reply other threads:[~2001-09-06 14:39 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 3:36 page_launder() on 2.4.9/10 issue Marcelo Tosatti
2001-08-28 18:07 ` Daniel Phillips
2001-08-28 18:17 ` Linus Torvalds
2001-08-30 1:36 ` Daniel Phillips
2001-09-03 14:57 ` Marcelo Tosatti
2001-09-04 15:26 ` Jan Harkes
2001-09-04 15:24 ` Marcelo Tosatti
2001-09-04 17:14 ` Jan Harkes
2001-09-04 15:53 ` Marcelo Tosatti
2001-09-04 19:33 ` Daniel Phillips
2001-09-06 11:52 ` Rik van Riel
2001-09-06 12:31 ` Daniel Phillips
2001-09-06 12:32 ` Rik van Riel
2001-09-06 12:53 ` Daniel Phillips
2001-09-06 13:03 ` Rik van Riel
2001-09-06 13:18 ` Kurt Garloff
2001-09-06 13:23 ` Rik van Riel
2001-09-06 13:28 ` Alan Cox
2001-09-06 13:29 ` Rik van Riel
2001-09-06 16:45 ` Daniel Phillips
2001-09-06 16:57 ` Rik van Riel
2001-09-06 17:22 ` Daniel Phillips
2001-09-06 19:25 ` Rik van Riel
2001-09-06 19:45 ` Daniel Phillips
2001-09-06 19:52 ` Rik van Riel
2001-09-07 0:32 ` Kurt Garloff
2001-09-06 19:53 ` Mike Fedyk
2001-09-06 17:35 ` Mike Fedyk
2001-09-06 13:10 ` Stephan von Krawczynski
2001-09-06 13:23 ` Alex Bligh - linux-kernel
2001-09-06 13:42 ` Stephan von Krawczynski
2001-09-06 14:01 ` Alex Bligh - linux-kernel
2001-09-06 14:39 ` Stephan von Krawczynski [this message]
2001-09-06 15:02 ` Alex Bligh - linux-kernel
2001-09-06 15:07 ` Rik van Riel
[not found] ` <Pine.LNX.4.33L.0109061206020.31200-100000@imladris.rielhome.con ectiva>
2001-09-06 15:16 ` Alex Bligh - linux-kernel
2001-09-06 15:10 ` Stephan von Krawczynski
2001-09-06 15:18 ` Alex Bligh - linux-kernel
2001-09-06 17:34 ` Daniel Phillips
2001-09-06 17:32 ` Alex Bligh - linux-kernel
2001-09-06 13:54 ` M. Edward Borasky
2001-09-06 14:39 ` Alan Cox
2001-09-06 16:20 ` Victor Yodaiken
2001-09-06 17:33 ` Daniel Phillips
2001-09-06 17:51 ` Daniel Phillips
2001-09-06 21:01 ` [RFC] Defragmentation proposal: preventative maintenance and cleanup [LONG] Alex Bligh - linux-kernel
2001-09-07 6:35 ` Daniel Phillips
2001-09-07 8:58 ` Alex Bligh - linux-kernel
2001-09-07 9:15 ` Alex Bligh - linux-kernel
2001-09-07 9:28 ` Alex Bligh - linux-kernel
2001-09-07 21:38 ` Daniel Phillips
2001-09-07 21:56 ` Daniel Phillips
2001-09-07 12:30 ` page_launder() on 2.4.9/10 issue Stephan von Krawczynski
2001-09-04 16:27 ` Rik van Riel
2001-09-04 17:13 ` Jan Harkes
2001-09-04 15:56 ` Marcelo Tosatti
2001-09-04 17:54 ` Jan Harkes
2001-09-04 16:37 ` Marcelo Tosatti
2001-09-04 18:49 ` Alan Cox
2001-09-04 19:39 ` Jan Harkes
2001-09-04 20:25 ` Alan Cox
2001-09-06 11:23 ` Rik van Riel
2001-09-04 19:54 ` Andrea Arcangeli
2001-09-04 18:36 ` Marcelo Tosatti
2001-09-04 20:10 ` Daniel Phillips
2001-09-04 22:04 ` Andrea Arcangeli
2001-09-05 2:41 ` Daniel Phillips
2001-09-06 11:18 ` Rik van Riel
2001-09-04 17:35 ` Daniel Phillips
2001-09-04 20:43 ` Jan Harkes
2001-09-06 11:21 ` Rik van Riel
[not found] <20010828180108Z16193-32383+2058@humbolt.nl.linux.org.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0108281110540.8754-100000@penguin.transmeta.com.suse.lists.linux.kernel>
2001-08-28 19:14 ` Andi Kleen
2001-08-28 20:01 ` David S. Miller
2001-08-28 20:49 ` Linus Torvalds
2001-08-28 20:56 ` David S. Miller
2001-08-29 13:48 ` Rik van Riel
2001-08-29 13:49 ` Linus Torvalds
2001-08-29 14:38 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 23:14 Samium Gromoff
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=20010906163909.186b8b46.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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