From: Benjamin LaHaise <bcrl@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Rik van Riel <riel@conectiva.com.br>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: throttling dirtiers
Date: Wed, 31 Jul 2002 17:14:56 -0400 [thread overview]
Message-ID: <20020731171456.S10270@redhat.com> (raw)
In-Reply-To: <3D48504B.9520455D@zip.com.au>; from akpm@zip.com.au on Wed, Jul 31, 2002 at 02:02:03PM -0700
On Wed, Jul 31, 2002 at 02:02:03PM -0700, Andrew Morton wrote:
> But let's back off a bit. The problem is that a process
> doing a large write() can penalise innocent processes which
> want to allocate memory.
>
> How to fix that?
First off, make it obvious where we block in the allocation path (pawning
off all memory reaping to kswapd et al is an easy first step here). Then
make allocators cycle through on a FIFO basis by using something like the
page reservation patch I came up with a while ago. That'll give us an
easy place to change scheduling behaviour.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
--
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-mm.org/
next prev parent reply other threads:[~2002-07-31 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 8:26 Andrew Morton
2002-07-31 20:06 ` William Lee Irwin III
2002-07-31 20:23 ` Benjamin LaHaise
2002-07-31 20:26 ` Rik van Riel
2002-07-31 20:59 ` William Lee Irwin III
2002-07-31 21:02 ` Andrew Morton
2002-07-31 21:14 ` Benjamin LaHaise [this message]
2002-07-31 21:25 ` Rik van Riel
2002-07-31 21:32 ` Andrew Morton
2002-07-31 21:55 ` Rik van Riel
2002-07-31 22:24 ` Andrew Morton
2002-07-31 22:32 ` Rik van Riel
2002-07-31 21:28 ` Andrew Morton
2002-07-31 21:35 ` Rik van Riel
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=20020731171456.S10270@redhat.com \
--to=bcrl@redhat.com \
--cc=akpm@zip.com.au \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=wli@holomorphy.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