public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: concurrent VM subsystems
Date: Thu, 25 Oct 2001 16:22:00 +0200	[thread overview]
Message-ID: <20011025162200.D631@marowsky-bree.de> (raw)
In-Reply-To: <freemail.20010925100655.37794@fm3.freemail.hu> <3BD7F44C.7020007@ndsu.nodak.edu>
In-Reply-To: <3BD7F44C.7020007@ndsu.nodak.edu>; from "Reid Hekman" on 2001-10-25T06:15:24

On 2001-10-25T06:15:24,
   Reid Hekman <reid.hekman@ndsu.nodak.edu> said:

> We've been over this already, while it would be nice for testing if the
> 
> two VM's could be compared without all the extra variables of the Linus
> and -ac trees it's not going to happen. It would be a big headache to 
> maintain all the extra source that would involve and all the changes to 
> other stuff you'd have to patch to make the two interchangeable. 

Now, this might be 2.5 material, but I think the subsystem should be
modularized; I think it has been proven that this part of the code is
definitely subject for discussion, and I would go as far as saying it just
might be possible that the optimal VM, catering to different approaches, plain
out doesn't exist, and that being able to switch VM personalities during
runtime would be useful.

Fortifying the subsystem borders would also make debugging and testing easier.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Perfection is our goal, excellence will be tolerated. -- J. Yahl


  reply	other threads:[~2001-10-25 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  8:06 concurrent VM subsystems Marton Kadar
2001-10-25 11:15 ` Reid Hekman
2001-10-25 14:22   ` Lars Marowsky-Bree [this message]
2001-10-25 13:06 ` Luigi Genoni
2001-10-25 13:52   ` M. Edward Borasky
2001-10-25 22:30     ` Luigi Genoni
2001-10-25 14:35   ` CaT
2001-10-25 22:35     ` Luigi Genoni
2001-10-26  0:33       ` CaT
2001-10-26  1:12       ` Rik van Riel

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=20011025162200.D631@marowsky-bree.de \
    --to=lmb@suse.de \
    --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