From: Philips <philips@iph.to>
To: linux-kernel@vger.kernel.org
Subject: Re: A Possible 2.5 Idea, maybe?
Date: Sat, 30 Jun 2001 14:08:08 +0300 [thread overview]
Message-ID: <3B3DB318.B799F4E3@iph.to> (raw)
In-Reply-To: <Pine.LNX.4.33.0106290753340.25959-100000@biglinux.tccw.wku.edu> <20010629164942.B21707@crosswinds.net>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Patrick Mauritz wrote:
>
> On Fri, Jun 29, 2001 at 08:17:25AM -0500, Brent D. Norris wrote:
> > Instead of forking the kernel or catering only to one group, instead why
> > not try this: Using the new CML2 tools and rulesets, make it possible to
> > have the kernel configured for the type of job it will be doing? Just
> > like CML2 asks our CPU type (i386, alpha, althon ...) and then goes out
> > and configures options for that, have it ask people "Is your machine a
> > server, workstation, embedded/handheld?" and configure things in the
> > kernel like the VM, bootup and others to optimize it for that job type?
> that could be the "easy == end-user" setup
> why can't there be two (possibly similar but tweaked) VMs (and other stuff as well)
> be in the source so everyone has to choose exactly one for his kernel?
>
there are patches for plug-able TCP/IP stacks.
filesystems are already plug-able (someone need journaling, some one needs
quoatas, some needs nothing).
there are patches for plug-able task scheduler.
If I could choose what filesystem to run on / - it impact performance greatly
- why can't I choose how my tasks are scheduled? how my packets are going to
NIC?
IMHO great idea. I think this will improve portability. And embeded guys will
be in permanent satisfaction ;-)
But I'm afraid this won't happen in 2.5 - this kind of change require well
defined and stable internal interfaces. So this is really huge amount of work.
This would be one little step toward the microkernel architecture (like Hurd).
Good again :-)
[-- Attachment #2: Card for Philips --]
[-- Type: text/x-vcard, Size: 407 bytes --]
begin:vcard
n:Filiapau;Ihar
tel;pager:+375 (0) 17 2850000#6683
tel;fax:+375 (0) 17 2841537
tel;home:+375 (0) 17 2118441
tel;work:+375 (0) 17 2841371
x-mozilla-html:TRUE
url:www.iph.to
org:Enformatica Ltd.;Linux Developement Department
adr:;;Kalinine str. 19-18;Minsk;BY;220012;Belarus
version:2.1
email;internet:philips@iph.to
title:Software Developer
note:(none)
x-mozilla-cpt:;18368
fn:Philips
end:vcard
next prev parent reply other threads:[~2001-06-30 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 13:17 Brent D. Norris
2001-06-29 14:49 ` Patrick Mauritz
2001-06-30 11:08 ` Philips [this message]
2001-06-30 11:17 ` Alexander Viro
2001-06-29 16:10 ` Dan Podeanu
2001-06-29 16:40 ` Brent D. Norris
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=3B3DB318.B799F4E3@iph.to \
--to=philips@iph.to \
--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®