linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andrea Arcangeli <andrea@suse.de>,
	linux-mm@kvack.org, "Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [highmem bug report against -test5 and -test6] Re: [PATCH] Re: simple FS application that hangs 2.4-test5, mem mgmt problem or FS buffer cache mgmt problem? (fwd)
Date: Mon, 2 Oct 2000 18:42:58 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0010021836090.1067-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.10.10010021429230.826-100000@penguin.transmeta.com>

On Mon, 2 Oct 2000, Linus Torvalds wrote:
> On Mon, 2 Oct 2000, Rik van Riel wrote:
> > 
> > OK, so we want something like the following in
> > refill_inactive_scan() ?
> > 
> > if (free_shortage() && inactive_shortage() && page->mapping &&
> > 			page->buffers)
> > 	try_to_free_buffers(page, 0);
> 
> That's just nasty.
> 
> Why not just do it unconditionally whenever we do the
> age_page_down_ageonly(page) too? Simply something like
> 
> 	if (page->buffers)
> 		try_to_free_buffers(page, 1);

You will want to add page->mapping too, so we won't be kicking
buffermem data out of memory when we don't need to.

Also, you really want to free the bufferheads on the pages that
are in heavy use (say glibc shared ages) too...

> (and yes, I think it should also start background writing - we
> probably need the gfp_mask to know whether we can do that).

Background writing is done by kupdate / kflushd.

> I hate code that tries to be clever. 

*nod*

You're right that my last idea was too complicated ;)

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
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-10-02 21:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-02 19:35 Rik van Riel
2000-10-02 19:56 ` Andrea Arcangeli
2000-10-02 19:59   ` Rik van Riel
2000-10-02 20:17     ` Andrea Arcangeli
2000-10-02 20:24       ` Rik van Riel
2000-10-02 21:16     ` Linus Torvalds
2000-10-02 20:06   ` Linus Torvalds
2000-10-02 20:16     ` Rik van Riel
2000-10-02 20:25     ` Ingo Molnar
2000-10-02 20:45       ` Rik van Riel
2000-10-02 21:21         ` Linus Torvalds
2000-10-02 21:27           ` Rik van Riel
2000-10-02 21:19       ` Linus Torvalds
2000-10-02 21:23         ` Rik van Riel
2000-10-02 21:31           ` Linus Torvalds
2000-10-02 21:42             ` Rik van Riel [this message]
2000-10-02 21:58               ` Linus Torvalds
2000-10-02 22:08                 ` Rik van Riel
2000-10-02 22:18                   ` Andrea Arcangeli
2000-10-02 22:23                     ` Rik van Riel
2000-10-02 23:06                     ` Linus Torvalds
2000-10-02 23:12                       ` Rik van Riel
2000-10-02 23:16                         ` Linus Torvalds
2000-10-02 23:20                       ` Andrea Arcangeli
2000-10-02 22:53                   ` Linus Torvalds
2000-10-02 23:06                     ` Rik van Riel
2000-10-02 23:14                       ` Linus Torvalds
2000-10-02 21:57         ` Ingo Molnar
2000-10-02 21:52           ` Rik van Riel
2000-10-02 22:53             ` Ingo Molnar
2000-10-02 23:01               ` Rik van Riel
2000-10-02 23:10                 ` Andrea Arcangeli
2000-10-02 23:29                 ` Ingo Molnar
2000-10-02 23:25                   ` Andrea Arcangeli
2000-10-02 23:32                     ` Linus Torvalds
2000-10-03 12:05                     ` Ingo Molnar

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.0010021836090.1067-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=andrea@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=sct@redhat.com \
    --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