public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Another question about thrashing
Date: Tue, 6 May 2003 15:18:24 -0700	[thread overview]
Message-ID: <20030506221824.GU8978@holomorphy.com> (raw)
In-Reply-To: <3EB7C490.5040803@techsource.com>

On Tue, May 06, 2003 at 10:20:00AM -0400, Timothy Miller wrote:
> There didn't seem to be much interest in my earlier post about kernel 
> behavior when swap thrashing.
> So my question is, are we not concerned about system behavior when one 
> process uses so much memory that it grinds everything else to a halt?
> It appears that a thrashing process is being given more preferential 
> treatment than it should.

Design characteristic of global page replacement algorithms. It's not
getting touched for 2.5/2.6


-- wli

      reply	other threads:[~2003-05-06 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 14:20 Another question about thrashing Timothy Miller
2003-05-06 22:18 ` William Lee Irwin III [this message]

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=20030506221824.GU8978@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.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