linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "John Fremlin" <vii@penguinpowered.com>
To: linux-mm@kvack.org
Subject: Re: [PATCH] Re: latancy test of -ac22-riel
Date: 23 Jun 2000 02:09:13 +0100	[thread overview]
Message-ID: <m2aegdqk3q.fsf@boreas.southchinaseas> (raw)
In-Reply-To: Rik van Riel's message of "Thu, 22 Jun 2000 16:47:50 -0300 (BRST)"

Rik van Riel <riel@conectiva.com.br> writes:

> You're confusing things here.

It wouldn't come as great shock to me :-)

But OTOH the patch does stop the annoying stalls so it must be doing
something right.

> If kswapd was too slow in freeing up memory, but there is
> still more memory available, then we should NOT kill a
> process but just stall the process until more memory is
> available.

Yes. What I was trying to get across was that we shouldn't waste a
timeslice trying to find pages to evict which are going to be read
back in next process switch (because most pages are impossible to swap
out).

[...]

Your solution (which is what they do in FreeBSD?) would be ideal, but
it wasn't in my kernel source (test1-ac22-riel).

[...]

-- 

	http://altern.org/vii
--
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-06-23  1:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19 23:57 [itcompilesshipitPATCH] -ac22-riel vm improvement? Rik van Riel
2000-06-20  0:11 ` Juan J. Quintela
2000-06-20  6:13 ` latancy test of -ac22-riel Roger Larsson
     [not found]   ` <m2u2eoxwzx.fsf@boreas.southchinaseas>
     [not found]     ` <394FB013.3B21EA28@norran.net>
2000-06-22 19:11       ` [PATCH] " John Fremlin
2000-06-22 19:47         ` Rik van Riel
2000-06-23  1:09           ` John Fremlin [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=m2aegdqk3q.fsf@boreas.southchinaseas \
    --to=vii@penguinpowered.com \
    --cc=linux-mm@kvack.org \
    /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