linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Rik van Riel <H.H.vanRiel@phys.uu.nl>,
	Jeffrey Hundstad <jeffrey.hundstad@mankato.msus.edu>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: useless report -- perhaps memory allocation problems in 2.1.12[678]
Date: Tue, 17 Nov 1998 17:41:51 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.3.95.981117174031.23128A-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.981117171051.1077V-100000@penguin.transmeta.com>



On Tue, 17 Nov 1998, Linus Torvalds wrote:
> 
> But whether kswapd should go page-synchronous at some point? Maybe. I can
> see arguments both for and against (the "for" argument is that we prefer
> to have more intense bouts of IO followed by a nice clean wait, while the
> "against" argument is that maybe we want to spread out the thing). 

Oh, well, I'm currently leaning for "for", which means your patch to
page_io.c is what I have now.. I don't like "trickling" pages by running
out of requests or something like that, so having the occasional nice wait
is probably best.

		Linus

--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

  reply	other threads:[~1998-11-18  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199811131746.LAA23512@mail.mankato.msus.edu>
1998-11-16 14:27 ` Rik van Riel
1998-11-17 11:21   ` Stephen C. Tweedie
1998-11-17 20:18     ` Rik van Riel
1998-11-17 23:14       ` Linus Torvalds
1998-11-18  1:09         ` Stephen C. Tweedie
1998-11-18  1:21           ` Linus Torvalds
1998-11-18  1:41             ` Linus Torvalds [this message]
1998-11-18  8:58               ` Rik van Riel
1998-11-18  9:19             ` Stephen C. Tweedie

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.3.95.981117174031.23128A-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=H.H.vanRiel@phys.uu.nl \
    --cc=jeffrey.hundstad@mankato.msus.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.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