From: Erik Tews <erik.tews@gmx.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Alok K. Dhir" <alok@dhir.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.6-pre2 VM
Date: Tue, 12 Jun 2001 23:02:21 +0200 [thread overview]
Message-ID: <20010612230220.A30693@mobile> (raw)
In-Reply-To: <Pine.LNX.4.21.0106120116250.14934-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0106120116250.14934-100000@imladris.rielhome.conectiva>
On Tue, Jun 12, 2001 at 01:17:05AM -0300, Rik van Riel wrote:
> On Mon, 11 Jun 2001, Alok K. Dhir wrote:
>
> > Just wondering - has anyone who was having issues with the VM
> > subsystem in 2.4.5 and a few versions below tried v2.4.6-pre2?
> > Is the problem reduced and/or resolved?
>
> The answer is both yes and no, depending on which VM problem
> you're talking about. ;)
What is about the problem that 2.4.x is swapping out too much? Are there
currently any patches for testing? Or are there some values in proc
which can change this bad vm-behaviour?
prev parent reply other threads:[~2001-06-12 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 2:41 2.4.6-pre2 VM Alok K. Dhir
2001-06-12 4:17 ` Rik van Riel
2001-06-12 2:51 ` Marcelo Tosatti
2001-06-12 21:02 ` Erik Tews [this message]
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=20010612230220.A30693@mobile \
--to=erik.tews@gmx.net \
--cc=alok@dhir.net \
--cc=linux-kernel@vger.kernel.org \
--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