linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trent Lloyd <lathiat@bur.st>
To: linux-kernel@vger.kernel.org
Cc: mkernel@linuxmail.org
Subject: Re: Rewrite Kernel
Date: Wed, 7 Apr 2004 22:04:50 +0800	[thread overview]
Message-ID: <20040407140448.GB17074@thump.bur.st> (raw)
In-Reply-To: <20040407125406.209FC39834A@ws5-1.us4.outblaze.com>

Hi Mohamed,

I am not sure if your intentions are real, but I am assuming they are.

Writing the linux kernel all in assembler would be almost impossible,
it has taken 10 years to get the kernel to the point it is in C, going
that all in ASM would be a) pointless and b) time consuming, your work
would be outdated before its done

Also, the technical know-how for such a task would be large, the kernel
is a collection of the knowledge, intelligence and time of hundreds of
people, I do not beleive one person could know or hold or the know how
for that (while some who do alot of hacking, linus, alan cox, etc may
know *alot*, i still don't beleive even they could do such a task)

However, if you are serious about something like this and have the
knowhow, time and will, you have a few options.

a) You could hack the kernel in C, including optimizing what is there,
making better algorithms of systems for doing things
b) You could convert some parts of the kernel to ASM for the i386 arch
specific stuff, if it can be as functional and have a usefull gain.
c) You could work on the GCC compiler for generating better assembly
code from the C output, I'm sure there are many areas this could be
improved.
d) You could work on libc, in a similar fassion to the above,
optimizing, fixing, improving and adding to it.

Best of luck with your adventures.

Cheers,
Trent
Bur.st

> i wanna to rewrite a version of linux kernel from scratch in assembly for intel 386+ fo speed and a libc also in assembly for speed
> what do u think guys

--
Trent "Lathiat" Lloyd <lathiat@bur.st>

Sixlabs.org (http://www.sixlabs.org/)
Bur.st Networking Inc. (http://www.bur.st/)

  parent reply	other threads:[~2004-04-07 14:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 12:54 Rewrite Kernel Mohamed Aslan
2004-04-07 12:57 ` viro
2004-04-07 12:59 ` Wichert Akkerman
2004-04-07 13:08 ` John Bradford
2004-04-07 13:13 ` Sean Neakums
2004-04-07 13:46   ` Dumitru Ciobarcianu
2004-04-07 13:58   ` Richard B. Johnson
2004-04-07 14:36     ` Nick Piggin
2004-04-07 18:58     ` Valdis.Kletnieks
2004-04-07 13:22 ` Zwane Mwaikambo
2004-04-07 13:56 ` Richard B. Johnson
2004-04-07 14:02 ` Erik Mouw
2004-04-07 14:04 ` Trent Lloyd [this message]
2004-04-07 14:27 ` Redeeman
2004-04-07 14:55   ` John Bradford
2004-04-07 15:05     ` Lars Marowsky-Bree
2004-04-07 15:17       ` John Bradford
2004-04-07 15:20       ` Emmanuel Fleury
2004-04-07 15:21       ` John Bradford
2004-04-07 17:21       ` Redeeman
2004-04-07 18:47         ` Paulo Marques
2004-04-07 18:12       ` Aaron Smith
2004-04-07 19:58         ` Måns Rullgård
2004-04-07 23:03           ` David B. Stevens
2004-04-08 10:34             ` David Weinehall
2004-04-07 14:57 ` Rob Couto
2004-04-13 14:03   ` Eric W. Biederman
2004-04-07 16:00 ` Brian Pawlowski
2004-04-10 16:59 ` J. Ryan Earl
2004-04-10 17:21   ` Denis Vlasenko
2004-04-10 19:57     ` J. Ryan Earl
2004-04-11 16:58       ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2004-04-07 13:05 Mohamed Aslan
2004-04-07 17:27 ` Robin Rosenberg
2004-04-24 13:24 Mohamed Aslan
2004-04-24 15:10 ` billy rose
2004-04-24 15:45 ` David B. Stevens

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=20040407140448.GB17074@thump.bur.st \
    --to=lathiat@bur.st \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkernel@linuxmail.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;
as well as URLs for NNTP newsgroup(s).