linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: riel@nl.linux.org
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Linux responsiveness under heavy load
Date: Wed, 8 Mar 2000 23:39:46 +0100	[thread overview]
Message-ID: <20000308233946.A9644@pcep-jamie.cern.ch> (raw)
In-Reply-To: <Pine.LNX.4.21.0003081920500.4639-100000@duckman.conectiva>; from Rik van Riel on Wed, Mar 08, 2000 at 07:26:22PM -0300

Rik van Riel wrote:
> > A larger priority for page-in I/O due to interactive process too
> > might help too.  Some modification of Andrea's elevator.  But
> > that doesn't seem so easy.
> 
> Read requests are easily tied to a process, so this could
> be relatively easy. Doing it properly before 2.5 may be a
> little difficult though ...

A simple flag with each I/O request meaning "high priority due to
interactive process I/O".  Make the elevator select high priority
requests before low ones, with the same sequence number bound for
fairness as has recently been implemented.

Maybe even a small holdoff time when going from handling a high priority
to a low priority request, to give the interactive process a few
microseconds to stimulate another page in.  (Actually a small holdoff in
general between I/O "here" and I/O "far away" might improve overall seek
times, orthogonal to priority issues).

It does seem too simple to work, but has anyone tried it?

-- Jamie
--
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-03-08 22:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000308223851.A9519@pcep-jamie.cern.ch>
2000-03-08 22:26 ` Rik van Riel
2000-03-08 22:39   ` Jamie Lokier [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=20000308233946.A9644@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.org \
    /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