From: John Gilmore <gnu@toad.com>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] non-blocking IO: Simplicity has been subtituted for efficiency
Date: Wed, 03 Jun 2020 18:24:52 -0700 [thread overview]
Message-ID: <8066.1591233892@hop.toad.com> (raw)
In-Reply-To: <20200602201334.95D9718C079@mercury.lcs.mit.edu>
Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> > I'm curious as to what the rationale was for Unix to have been designed
> > with basic I/O being blocking rather than asynchronous.
>
> It's a combination of two factors, I reckon. One, which is better depends a
> lot on the type of thing you're trying to do. For many typical thing (e.g.
> 'ls'), blocking is a good fit. And, as As Arnold says, asyhchronous I/O is
> more complicated, and Unix was (well, back then at least) all about getting
> the most bang for the least bucks.
I just happened to open a binder today of old papers about UNIX(tm),
including Ken Thompson's "Unix Implementation" paper, which says at the
bottom of the introduction:
"What is or is not implemented in the kernel represents both a great
responsibiity and a great power. It is a soap-box platform on "the
way things should be done." Even so, if "the way" is too radical, no
one will follow it. Every important decision was weighted carefully.
Throughout, simplicity has been substituted for efficiency. Complex
algorithms are used only if their complexity can be localized."
John
next prev parent reply other threads:[~2020-06-04 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 20:13 [TUHS] non-blocking IO Noel Chiappa
2020-06-02 20:43 ` Clem Cole
2020-06-02 22:14 ` Rich Morin
2020-06-03 16:31 ` Paul Winalski
2020-06-03 19:19 ` John P. Linderman
2020-06-04 1:24 ` John Gilmore [this message]
2020-06-04 6:27 ` [TUHS] non-blocking IO: Simplicity has been subtituted for efficiency arnold
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=8066.1591233892@hop.toad.com \
--to=gnu@toad.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.tuhs.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).