linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-mm@kvack.org
Subject: Re: pre8: where has the anti-hog code gone?
Date: Sun, 14 May 2000 10:45:42 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.05.10005141023530.2330-100000@fenrus.demon.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10005132035370.2422-100000@penguin.transmeta.com>

> > My idea is (but I have not tested this) that for priority == 0 (aka "Uh oh")
> > shrink_mmap or do_try_to_free_pages have to block while waiting for pages to
> > be commited to disk. As far as I can see, shrink_mmap just skips pages that
> > are being commited to disk, while these could be freed when they are waited
> > upon. 

> probably fine, and you could try to just change "sync_page_buffers()" back
> to the code that did 
> 
> 	if (buffer_locked(p))
> 		__wait_on_buffer(p);
> 	else if (buffer_dirty(p))
> 		ll_rw_block(WRITE, 1, &p);
> 
> (instead of the current "buffer_dirty(p) && !buffer_locked(p)" test that
> only starts the IO).

I changed this a bit, so that the __wait_on_buffer only gets called for
do_try_to_free_pages priority 0. With this, mmap002 doesn't OOM anymore. 


> How does it feel performance-wise?

This is a bit hard to say, as my testbox is headless. However, I started
Netscape on it (over a 100Mbit network) and did a "make -j2 bzImage" at
the same time. Netscape didn't seem to suffer, but there was usually about
30 megabytes[1] ram free (according to "top"), so maybe it is to agressive
in freeing memory.

Greetings,
   Arjan van de Ven

[1] The machine has 96 Mb total ram

--
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-05-14  8:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-12 23:37 Rik van Riel
2000-05-13 15:28 ` Linus Torvalds
2000-05-13 18:14   ` Juan J. Quintela
2000-05-13 21:24   ` Arjan van de Ven
2000-05-13 21:59     ` Juan J. Quintela
2000-05-14  3:41     ` Linus Torvalds
2000-05-14  8:45       ` Arjan van de Ven [this message]
2000-05-15  1:37         ` Linus Torvalds
2000-05-14 10:52   ` Ingo Molnar
2000-05-14 10:55     ` Ingo Molnar
2000-05-14 11:28     ` Ingo Molnar
2000-05-14 12:01       ` Rik van Riel
2000-05-14 12:12         ` Ingo Molnar
2000-05-14 12:19         ` Ingo Molnar
2000-05-15 14:50 Mark_H_Johnson.RTS
2000-05-15 15:58 ` Rik van Riel
2000-05-15 16:01 ` Linus Torvalds

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.05.10005141023530.2330-100000@fenrus.demon.nl \
    --to=arjan@fenrus.demon.nl \
    --cc=linux-mm@kvack.org \
    --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