public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xuan Baldauf <xuan--lkml@baldauf.org>
To: linux-kernel@vger.kernel.org
Subject: dynamic swap prioritizing
Date: Wed, 10 Oct 2001 00:01:13 +0200	[thread overview]
Message-ID: <3BC373A8.CD94917B@baldauf.org> (raw)

Hello,

I have a linux box with 3 harddisks of different
characteristics (size, seek time, throughput), each capable
of holding a swap partition. Sometimes, one harddisk is
driven heavily (e.g. database application), sometimes, the
other harddisk is busy.

I imagine following optimization:
- all swap partitions have the same priority from the start
on
- runtime statistics are gathered covering response time
(time from page request to availability)
- the fastest drive is used first (or maybe in striping mode
parallely woth the second-fastest drive)
- because the fastest drive will be more busy, its response
times will rise, reaching equality with other drives
- at that point, other drives are also considered for
swapout
- that system regularily adapts its decisions based on
recent statistics ("recent" is a tuning parameter)

Such an algorithm also would properly prioritize
network-swap and video-memory-swap, reducing time and cost
of a manual priority configuration (and statistics
gathering).

Does the linux kernel already implement such an
optimization? Is it planned?

Xuân.



             reply	other threads:[~2001-10-09 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 22:01 Xuan Baldauf [this message]
2001-10-10  1:43 ` dynamic swap prioritizing Rik van Riel
2001-10-10  3:35 ` Andreas Dilger
2001-10-10  8:38 ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10 15:23 Venkatesh Ramamurthy
2001-10-10 15:55 ` 'adilger@turbolabs.com'
2001-10-10 17:14   ` Richard B. Johnson
2001-10-12  0:45   ` Xuan Baldauf
2001-10-12  3:32     ` 'adilger@turbolabs.com'
2001-10-12 15:22       ` Xuan Baldauf
2001-10-10 16:47 Venkatesh Ramamurthy

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=3BC373A8.CD94917B@baldauf.org \
    --to=xuan--lkml@baldauf.org \
    --cc=linux-kernel@vger.kernel.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