public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: klink@clouddancer.com (Colonel), linux-kernel@vger.kernel.org
Subject: Re: What are the VM motivations??
Date: Mon, 25 Jun 2001 06:04:45 +0200	[thread overview]
Message-ID: <01062506044500.16624@starship> (raw)
In-Reply-To: <20010621190103.A888@jmcmullan.resilience.com> <9h6916$4og$1@ns1.clouddancer.com> <20010625034427.65260784D9@mail.clouddancer.com>
In-Reply-To: <20010625034427.65260784D9@mail.clouddancer.com>

On Monday 25 June 2001 05:44, Colonel wrote:
> 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 suggest 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.

Well, if you try that strategy you'll find you never get around to posting it 
because you'll be too worried about getting it right.  The point is not to 
get it right, it's to get a starting point down on (virtual) paper.  I'd 
strongly suggest passing something like that around for comment privately 
first.

*Then* post it.

(and convince me you're not just talking)

--
Daniel

  reply	other threads:[~2001-06-25  4:01 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
2001-06-25  4:04           ` Daniel Phillips [this message]
     [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=01062506044500.16624@starship \
    --to=phillips@bonn-fries.net \
    --cc=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