From: David Ford <david@blue-labs.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>,
"Richard B. Johnson" <root@chaos.analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: Ongoing 2.4 VM suckage
Date: Fri, 03 Aug 2001 13:59:22 -0400 [thread overview]
Message-ID: <3B6AE67A.9060709@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108021728130.5582-100000@duckman.distro.conectiva>
If it is that badly broken, isn't that sufficient criteria to justify
the patch?
Yes, I have experienced this frustration many times myself.
David
Rik van Riel wrote:
>On Thu, 2 Aug 2001, Rik van Riel wrote:
>
>>On Thu, 2 Aug 2001, Jeffrey W. Baker wrote:
>>
>>>I'm about the zillionth person to complain about this problem on
>>>this list. It is completely unacceptable to say that I can't
>>>use the memory on my machines because the kernel is too hungry
>>>for cache.
>>>
>>Fully agreed. The problem is that getting a solution which
>>works in a multizoned VM isn't all that easy, otherwise we
>>would have fixed it ages ago ...
>>
>
>Well, actually there are a few known solutions to this
>problem, but they are not really an option for the 2.4
>series since they require large code changes...
>
next prev parent reply other threads:[~2001-08-03 18:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 18:29 Ongoing 2.4 VM suckage Jeffrey W. Baker
2001-08-02 18:52 ` Richard B. Johnson
2001-08-02 19:10 ` Jeffrey W. Baker
2001-08-02 19:54 ` Richard B. Johnson
2001-08-02 20:10 ` Jeffrey W. Baker
2001-08-02 20:16 ` Rik van Riel
2001-08-02 20:28 ` Rik van Riel
2001-08-03 17:59 ` David Ford [this message]
2001-08-03 20:53 ` Rik van Riel
2001-08-03 21:59 ` Mike Black
2001-08-03 22:08 ` Rik van Riel
2001-08-04 1:06 ` Daniel Phillips
2001-08-03 23:58 ` [PATCH] Disable kswapd through proc (was Ongoing 2.4 VM suckage) Daniel Phillips
2001-08-04 7:21 ` Ongoing 2.4 VM suckage Stephen Satchell
2001-08-06 8:55 ` Helge Hafting
2001-08-06 16:37 ` Jeremy Linton
2001-08-07 7:51 ` David Weinehall
2001-08-03 22:47 ` David Ford
2001-08-02 21:01 ` Richard B. Johnson
2001-08-02 21:11 ` Jeffrey W. Baker
2001-08-02 21:44 ` Jakob Østergaard
2001-08-02 21:52 ` Jeffrey W. Baker
2001-08-02 21:56 ` Miles Lane
2001-08-02 22:05 ` Jeffrey W. Baker
2001-08-02 22:07 ` Rik van Riel
2001-08-02 22:17 ` Jeffrey W. Baker
2001-08-02 22:27 ` Rik van Riel
2001-08-02 22:32 ` Jeffrey W. Baker
2001-08-02 22:56 ` BERECZ Szabolcs
2001-08-03 13:07 ` jlnance
2001-08-03 13:31 ` Richard B. Johnson
2001-08-06 13:22 ` Luigi Genoni
2001-08-06 13:29 ` David S. Miller
2001-08-02 23:46 ` Ongoing 2.4 VM suckage pagemap_lru_lock Jeremy Linton
2001-08-02 22:15 ` Ongoing 2.4 VM suckage Pavel Zaitsev
2001-08-02 22:20 ` Jakob Østergaard
2001-08-03 12:04 ` Anders Peter Fugmann
2001-08-03 16:03 ` Rik van Riel
2001-08-03 16:24 ` Anders Peter Fugmann
2001-08-03 21:24 ` Rik van Riel
2001-08-03 22:00 ` Anders Peter Fugmann
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=3B6AE67A.9060709@blue-labs.org \
--to=david@blue-labs.org \
--cc=jwbaker@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=root@chaos.analogic.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