public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: What are the VM motivations??
Date: Sun, 24 Jun 2001 20:44:27 -0700 (PDT)	[thread overview]
Message-ID: <20010625034427.65260784D9@mail.clouddancer.com> (raw)
In-Reply-To: <9h6916$4og$1@ns1.clouddancer.com>
In-Reply-To: <20010621190103.A888@jmcmullan.resilience.com>    <20010624140114.A10745@jmcmullan.resilience.com>    <3B3697FB.3B7F098@247media.com> <01062504534600.16346@starship> <3B3697FB.3B7F098@247media.com> <9h6916$4og$1@ns1.clouddancer.com>

In clouddancer.list.kernel, you wrote:
>
>On Monday 25 June 2001 03:46, Russell Leighton wrote:
>> I read this thread as asking the question:
>>
>>     If VM management is viewed as an optimization problem,
>>     then what exactly is the function that you are optimizing and what are
>> the constraints?
>>
>> If you could express that well with a even a very loose model, then
>> the code could be reviewed to see if it was really doing what was intended
>> and assumptions could be tested.
>
>May I suggested an algorithm?
>
>  - Write down what you think the optimization constraints are.
>    (be specific, for example, enumerate all the flavors of page types -
>    process code, process data, page cache file data, page cache swap
>    cache, anonymous, shmem, etc.)
>
>  - Write down what you think the current algorithms are.
>    (again, be specific, use file names, function names, pseudocode and 
>    snippets of existing code.)
>
>  - Send it to Rik.  He'll tell you if it's right.

POST IT.  Give the rest of us some clues and the opportunity to check
evaluator's replies.

  parent reply	other threads:[~2001-06-25  3:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
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
     [not found]       ` <9h6916$4og$1@ns1.clouddancer.com>
2001-06-25  3:44         ` Colonel [this message]
2001-06-25  4:04           ` Daniel Phillips
     [not found]           ` <9h6d6b$509$1@ns1.clouddancer.com>
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
     [not found] ` <9h4vln$2tg$1@ns1.clouddancer.com>
2001-06-24 16:15   ` Colonel
2001-06-24 16:34     ` Rik van Riel
2001-06-24 19:11       ` Henning P. Schmiedehausen
     [not found]     ` <9h54u8$341$1@ns1.clouddancer.com>
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=20010625034427.65260784D9@mail.clouddancer.com \
    --to=klink@clouddancer.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