From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: [9fans] spreading the word
Date: Mon, 23 Feb 2009 15:39:38 -0800 [thread overview]
Message-ID: <b2156092068cd73e082f23236ad92084@mail.nanosouffle.net> (raw)
In-Reply-To: 9ad6c896cc1ad905714b3c2255a1dbf4@coraid.com
[-- Attachment #1: Type: text/plain, Size: 129 bytes --]
No discussion involving Einstein and Ken should have spelling mistakes
in the topic.
It complicates the understanding
ak
[-- Attachment #2: Type: message/rfc822, Size: 3529 bytes --]
From: erik quanstrom <quanstro@coraid.com>
To: me@acm.jhu.edu, 9fans@9fans.net
Subject: Re: [9fans] spreding the word
Date: Mon, 23 Feb 2009 17:20:45 -0500
Message-ID: <9ad6c896cc1ad905714b3c2255a1dbf4@coraid.com>
On Mon Feb 23 17:02:29 EST 2009, me@acm.jhu.edu wrote:
> >if you're after the historical progression of how the
> >structure of the kernel evolved, the file server kernel
> >is much more interesting.
>
> Any bits in particular? Any reason why?
port/proc.c is very interesting, as are pc/lock.c
and pc/trap.c.
they are all very interesting as they illustrate
the same concepts the pc kernel deals with, but
they are substatially simplier. i fear i've complicated
things a bit. hardware is more complicated these
days.
naturally, the fs kernel is less capable. it lacks
dynamic memory, for example. but the beauty
is that it doesn't need those things. i think it's
an interesting study in tradeoffs.
einstein said "make everything as simple as
possible, but not simpler". i think ken's take
is that if it's not simple enough, you're solving
the wrong problem.
- erik
next reply other threads:[~2009-02-23 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 23:39 Akshat Kumar [this message]
2009-02-23 23:46 ` erik quanstrom
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=b2156092068cd73e082f23236ad92084@mail.nanosouffle.net \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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).