9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: what about microkernel?
Date: Wed, 10 Oct 2007 11:26:55 -0700	[thread overview]
Message-ID: <3e1162e60710101126g4d096d8cj37d84d002909b11f@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0710081318s6e03e831i1905e00e479bd006@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

On 10/8/07, Eric Van Hensbergen <ericvh@gmail.com> wrote:
>
> On 10/8/07, Charles Forsyth <forsyth@terzarima.net> wrote:
> >
> > >That being said however, any advantages we can get on the relatively
> > >slow hardware should benefit the efficiency (if not the latency and
> performance) of the faster
> >
> > i think there's quite a bit of scope for performance improvements
> without doing violence
> > to the overall structure or messing up the implementation.  i hope some
> things end up
> > being smaller and cleaner.
> >
>
> Agreed.  Performance does not necessarily equal complexity.  Neither
> does allowing specialization -- I think specialization enables
> simplification and clarity in many situations.
>
>        -eric
>


Looks like at&t's new tilt is running L4/Linux :-)

Based on a qualcomm chipset I'd bet it's either Iguana based or something
else.

Buddy of mine posted this:

http://paste.lisp.org/display/48981

Not so strangely, it's using the version of gcc I had to use to build
pistachio on the G5 that Ron couldn't get going with whatever was on his Red
Hat system :-)

Dave

[-- Attachment #2: Type: text/html, Size: 1937 bytes --]

  reply	other threads:[~2007-10-10 18:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06 13:25 [9fans] " Andrew Wingorodov
2007-10-06 16:07 ` Lorenzo Fernando Bivens de la Fuente
2007-10-06 16:08 ` johnny
2007-10-06 16:26 ` Charles Forsyth
2007-10-06 20:24   ` [9fans] " Andrew Wingorodov
2007-10-06 20:50     ` Charles Forsyth
2007-10-07 16:18       ` David Leimbach
2007-10-07 16:30         ` ron minnich
2007-10-07 18:05           ` erik quanstrom
2007-10-07 20:28           ` David Leimbach
2007-10-07 20:49             ` Francisco J Ballesteros
2007-10-08 13:20               ` LiteStar numnums
2007-10-08 13:27                 ` Charles Forsyth
2007-10-08 14:50                 ` erik quanstrom
2007-10-08 15:58                   ` Eric Van Hensbergen
2007-10-08 16:01                     ` Francisco J Ballesteros
2007-10-08 17:16                     ` erik quanstrom
2007-10-08 19:14                       ` Eric Van Hensbergen
2007-10-08 19:53                         ` Charles Forsyth
2007-10-08 20:18                           ` Eric Van Hensbergen
2007-10-10 18:26                             ` David Leimbach [this message]
2007-10-10 20:42                               ` ron minnich
2007-10-10 21:38                                 ` David Leimbach
2007-10-08 17:46                     ` Charles Forsyth
2007-10-08 18:39                       ` David Leimbach
2007-10-08 19:11                       ` Eric Van Hensbergen
2007-10-08 18:34                     ` David Leimbach
2007-10-07 16:31         ` LiteStar numnums
2007-10-07 18:36         ` Andrew Wingorodov
2007-10-07 18:54           ` LiteStar numnums
2007-10-07 20:20           ` David Leimbach
2007-10-13  7:08 ` Andrew Wingorodov

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=3e1162e60710101126g4d096d8cj37d84d002909b11f@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).