linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason McMullan <jmcmullan@linuxcare.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Jason McMullan <jmcmullan@linuxcare.com>, linux-kernel@vger.kernel.org
Subject: Re: What are the VM motivations??
Date: Sun, 24 Jun 2001 16:29:09 -0400	[thread overview]
Message-ID: <20010624162909.A25106@jmcmullan.resilience.com> (raw)
In-Reply-To: <20010624145200.A14534@jmcmullan.resilience.com> <Pine.LNX.4.33L.0106241628100.23112-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0106241628100.23112-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Sun, Jun 24, 2001 at 04:29:09PM -0300

On Sun, Jun 24, 2001 at 04:29:09PM -0300, Rik van Riel wrote:
> Over the last year there has been quite a bit of discussion
> with Stephen Tweedie, Matt Dillon and more people. Parts of
> it can be found on http://linux-mm.org/
> 
> The conclusion of most of this discussion is in my FREENIX
> paper, which can be found at http://www.surriel.com/lectures/.

	[Just finished reading your paper, and hit the linux-mm.org site]

	Good overview of the Linux 2.4 VM. Although I do
have some questions...

	* When was the 'FREENIX' paper published? I could find
	  no date for it.

	* What workloads would you recommend for testing whether
	  a VM is 'well balanced' or not?

	* Would it be reasonable to have different 'default'
	  tunings for the kernel's VM based upon memory/swap
	  size/bandwidth? Personally, I feel that swap bandwidth
	  is an oft overlooked parameter in estimating VM performance.

-- 
Jason McMullan, Senior Linux Consultant
Linuxcare, Inc. 412.432.6457 tel, 412.656.3519 cell
jmcmullan@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Putting open source to work.

  reply	other threads:[~2001-06-24 20:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9h6916$4og$1@ns1.clouddancer.com>
2001-06-21 23:01 ` What are the VM motivations?? Jason McMullan
2001-06-21 23:32   ` [OT] " Justin Guyett
2001-06-22  1:13     ` Rik van Riel
2001-06-22  0:23   ` Rik van Riel
2001-06-23 20:23     ` watermodem
2001-07-01 23:58       ` Mark H. Wood
2001-06-23  2:03   ` Marcelo Tosatti
2001-06-24 15:04   ` Rik van Riel
2001-06-24 18:01     ` Jason McMullan
2001-06-24 18:26       ` Rik van Riel
2001-06-24 18:52         ` Jason McMullan
2001-06-24 19:29           ` Rik van Riel
2001-06-24 20:29             ` Jason McMullan [this message]
2001-06-24 20:49               ` Rik van Riel
2001-06-24 20:39             ` Jonathan Morton
2001-06-24 20:33       ` Stephen Satchell
2001-06-25  1:46       ` Russell Leighton
2001-06-25  2:53         ` Daniel Phillips
2001-06-25  3:44           ` Colonel
2001-06-25  4:04             ` Daniel Phillips
2001-06-25 15:46               ` Colonel
2001-06-25 16:25                 ` Daniel Phillips
2001-06-25 17:53                 ` Rik van Riel
2001-06-25 17:48             ` Rik van Riel
2001-06-24 16:15   ` Colonel
2001-06-24 16:34     ` Rik van Riel
2001-06-24 19:11       ` Henning P. Schmiedehausen
2001-06-25  3:40     ` Colonel
2001-07-01 14:43   ` Mark H. Wood

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=20010624162909.A25106@jmcmullan.resilience.com \
    --to=jmcmullan@linuxcare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).