linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ben LaHaise <bcrl@redhat.com>
To: "Juan J. Quintela" <quintela@fi.udc.es>
Cc: linux-mm@kvack.org, torvalds@transmeta.com
Subject: Re: [rtf] [patch] 2.3.99-pre6-3 overly swappy
Date: Thu, 20 Apr 2000 22:54:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0004202247170.9178-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <ytt4s8wb8rd.fsf@vexeta.dc.fi.udc.es>

On 21 Apr 2000, Juan J. Quintela wrote:

>    I have tried to mix the two, yours and him, and no way, the system
>    begins working OK, but in some moments, the system begins to trash
>    (very heavily).  Indeed I boot the machine with mem=64MB (normally
>    with 256MB), the same precesses for testing and the machine dies
>    in the middle of the trashing (no keyboard, no mouse, no response)
>    and the disk sound very loud.

Ahh, I'd expect this to be the case.  We're both going after the same
problem, by tuning the aggressiveness of the different parts of the vm
code.  Note that the patch I posted earlier is completely broken on
machines that don't have the majority of their memory above 16MB, but it's
atleast giving us a hint about what direction we need to go in.

One of the things that really needs fixing is the allocator's way of
choosing which zone to pressure for memory: most allocators don't care if
it's dma/not memory but the call to try_to_free_pages specifies a zone --
which may be the wrong one. :(

		-ben

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-04-21  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-20 19:43 Ben LaHaise
2000-04-20 20:13 ` Rik van Riel
2000-04-21  0:25 ` Juan J. Quintela
2000-04-21  2:54   ` Ben LaHaise [this message]
2000-04-21 17:50     ` Juan J. Quintela
2000-04-22 18:14       ` Juan J. Quintela

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=Pine.LNX.4.21.0004202247170.9178-100000@devserv.devel.redhat.com \
    --to=bcrl@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=quintela@fi.udc.es \
    --cc=torvalds@transmeta.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