linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Leighton <russell.leighton@247media.com>
To: Jason McMullan <jmcmullan@linuxcare.com>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: What are the VM motivations??
Date: Sun, 24 Jun 2001 21:46:36 -0400	[thread overview]
Message-ID: <3B3697FB.3B7F098@247media.com> (raw)
In-Reply-To: <20010621190103.A888@jmcmullan.resilience.com> <Pine.LNX.4.21.0106241203420.7419-100000@imladris.rielhome.conectiva> <20010624140114.A10745@jmcmullan.resilience.com>


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.

This seems like a reasonable request.

Jason McMullan wrote:

> On Sun, Jun 24, 2001 at 12:04:43PM -0300, Rik van Riel wrote:
> > OK.  I challenge you to come up with:
> >
> > 1) the set of inputs for the neural network
> > 2) the set of outputs
> > 3) the goal for training the thing
> >
> > I'm pretty fed up with people who want to "change the VM"
> > but never give any details of their ideas.
>
>         Uhh. That's not what I was ranting about. What I was
> ranting about is that we have never 'put to paper' the
> requirements ('motiviations') for a good VM, nor have we
> looked at said nonexistent list and figured out what instrumentation
> would be needed.
>
>         I don't now that much about VM, but I do know a bunch of
> people each scratching their own itch, and most of them not looking
> at the bigger picture. Linus, RvR, etc. excepted. Mostly. ;^)
>
>         The whole 'neural network' bit was mostly troll. Sorry,
> I got a little carried away at that point.
>
> --
> 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.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
---------------------------------------------------
Russell Leighton    russell.leighton@247media.com
---------------------------------------------------



  parent reply	other threads:[~2001-06-25  1:43 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
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 [this message]
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=3B3697FB.3B7F098@247media.com \
    --to=russell.leighton@247media.com \
    --cc=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).