All of lore.kernel.org
 help / color / mirror / Atom feed
From: "'adilger@turbolabs.com'" <adilger@turbolabs.com>
To: Venkatesh Ramamurthy <Venkateshr@ami.com>
Cc: "'xuan--lkml@baldauf.org'" <xuan--lkml@baldauf.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: dynamic swap prioritizing
Date: Wed, 10 Oct 2001 09:55:36 -0600	[thread overview]
Message-ID: <20011010095536.C10443@turbolinux.com> (raw)
In-Reply-To: <1355693A51C0D211B55A00105ACCFE6402B9E013@ATL_MS1>
In-Reply-To: <1355693A51C0D211B55A00105ACCFE6402B9E013@ATL_MS1>

On Oct 10, 2001  11:23 -0400, Venkatesh Ramamurthy wrote:
> > If this is to be generally useful, it would be good to find things
> > like max sequential read speed, max sequential write speed, and max
> > seek time (at least). Estimates for max sequential read speed and
> > seek time could be found at boot time for each disk relatively
> > easily, but write speed may have to be found only at runtime (or
> > it could all be fed in to the kernel from user space from benchmarks
> > run previously).
> 
> Maybe we can find out the statistics for the first time (or when swap is
> created) and store this information in the swap partition itself. This would
> allow us to compute time consuming statistics only once. Also we need to
> create new fields in the swap structure for this purpose.

I'd rather just have the statistic data in a regular file for ALL disks,
and then send it to the kernel via ioctl or write to a special file that
the kernel will read from.  I don't think it is critical to have this
data right at boot time, since it would only be used for optimizing I/O
access and would not be required for a disk to actually work.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-10-10 15:56 UTC|newest]

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

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=20011010095536.C10443@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=Venkateshr@ami.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xuan--lkml@baldauf.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 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.