mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason McMullan <jmcmullan@linuxcare.com>
To: linux-kernel@vger.kernel.org
Subject: What are the VM motivations??
Date: Thu, 21 Jun 2001 19:01:03 -0400	[thread overview]
Message-ID: <20010621190103.A888@jmcmullan.resilience.com> (raw)

<rant>

	I've been reading the VM thread off-and-on for, oh, the last
8 _years_ on linux-kernel. It doesn't seem that much progress gets
made in any one direction. For every throughput optimination for servers,
the desktop people yell 'interactivity'. For every 'long-disk-idle'
desire the laptop guys have, others want large buffer caches.

	It goes back and forth. Everybody pulling from all sides, and
the VM performance has stayed (mostly) in the center.

	Well, I have an idea. Let's take a page from the Neural
Network guys (not the code, just the ideas), and look at VM from a
motivational perspective.

	What if the VM were your little Tuxigachi. A little critter
that lived in your computer, handling all the memory, swap, and
cache management. What would be the positive and negative feedback
you'd give him to tell him how well he's doing VM?

	Here's a short, off-the-cuff list that hopefully most
everyone can agree on.

	Positive
	--------
		* Low system CPU load for the VM timeslice
		* Process IO requests / Disk IO is less than 1.0
		* Large idle times between disk activity
		* Process don't have to wait long for pages from VM.
		* etc.

	Negative
	--------
		* High CPU usage for VM
		* High disk IO for low number of process IO requests.
		* Disk is rarely idle
		* Processes stall for a long time waiting for VM.
		* Deadlocks (fatal!)
		* etc.

	One we know how we would 'train' our little VM critter, we 
will know how to measure its performance. Once we have measures, we
can have good benchmarks. Once we have good benchmarks - we can pick
a good VM alg. 

	Or heck, let's just make the VM a _real_ Neural Network, that
self trains itself to the load you put on the system. Hideously
complex and evil? Well, why not wire up that roach on the floor, eating
that stale cheese doodle. It can't do any worse job on VM that some of the
VM patches I've seen...

</rant>

-- 
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-21 23:17 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 ` Jason McMullan [this message]
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
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=20010621190103.A888@jmcmullan.resilience.com \
    --to=jmcmullan@linuxcare.com \
    --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

all inboxes | Powered by JetHome®