From: Pavel Machek <pavel@suse.cz>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Gustafson, Geoffrey R" <geoffrey.r.gustafson@intel.com>,
"'Andy Pfiffer'" <andyp@osdl.org>,
cgl_discussion@osdl.org, "Rhoads, Rob" <rob.rhoads@intel.com>,
hardeneddrivers-discuss@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Hardeneddrivers-discuss] RE: [cgl_discussion] Some Initial Comments on DDH-Spec-0.5h.pdf
Date: Mon, 30 Sep 2002 06:40:40 +0000 [thread overview]
Message-ID: <20020930064039.A159@toy.ucw.cz> (raw)
In-Reply-To: <3D8FC2DA.3010107@pobox.com>; from jgarzik@pobox.com on Mon, Sep 23, 2002 at 09:41:46PM -0400
Hi!
> > Most of what makes a 'good' driver is common for all purposes - things you
> > mention like don't make the system hang, don't cause fatal exceptions. But
> > there are some things that would be different between a desktop, embedded
> > system, enterprise server, or carrier server. For instance, when there is a
> > tradeoff between reliability and performance; when reliability is king, it
> > might be wise to do an insane amount of parameter checking to offset the
> > merest chance of an undetected bug crashing a system.
>
> This is not a valid example. We do not make tradeoffs between
> performance and reliability. Reliability _always_ comes first. If it
> did not, it's a bug.
No. We do run all drivers in *one* addressspace. That's bad for reliability.
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
prev parent reply other threads:[~2002-10-01 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDC461A30AC4D511ADE10002A5072CAD01FD8CEA@orsmsx119.jf.intel.com>
2002-09-24 1:41 ` [Hardeneddrivers-discuss] RE: [cgl_discussion] Some Initial Comments on DDH-Spec-0.5h.pdf Jeff Garzik
2002-09-24 6:33 ` Eric W. Biederman
2002-09-24 7:01 ` Jeff Garzik
2002-09-25 3:54 ` Andre Hedrick
2002-09-25 7:12 ` Eric W. Biederman
2002-09-30 6:40 ` Pavel Machek [this message]
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=20020930064039.A159@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=andyp@osdl.org \
--cc=cgl_discussion@osdl.org \
--cc=geoffrey.r.gustafson@intel.com \
--cc=hardeneddrivers-discuss@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.rhoads@intel.com \
/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).