All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Benjamin LaHaise <bcrl@redhat.com>
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 14:28:47 -0700	[thread overview]
Message-ID: <3D48568F.B7A006A7@zip.com.au> (raw)
In-Reply-To: 20020731171456.S10270@redhat.com

Benjamin LaHaise wrote:
> 
> 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.

None of that will preferentially throttle the source of
dirty pages, which seems a good thing to do?
--
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/

  parent reply	other threads:[~2002-07-31 21:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31  8:26 throttling dirtiers 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
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 [this message]
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=3D48568F.B7A006A7@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=bcrl@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.