From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] I/O load crashes Qemu
Date: Sat, 14 Jun 2008 17:01:30 -0700 [thread overview]
Message-ID: <20080615000130.87BDA5B5B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 14 Jun 2008 10:15:37 EDT." <1ffd3f9abf6e39e95f3bfdb7cdca0a10@quanstro.net>
> >> i find there's a certain simplicty in dealing directly
> >> with hardware, provided one has documentation.
> >
> > Provided it is complete and the h/w well designed and
> > interface regular. Unfortunately not all that common.
>
> you continue with this claim without presenting evidence.
...
> for example, the intel 82598 10gbe is a beast of a part.
> 341 pages of documentation. 200 registers. yet it's a
> simple driver because
...
> 3. most complicated functionality was ignored;
I rest my case :-)
How much simpler it would've been if instead of 200 registers
there was just a <cmd,arg-block-ptr> fifo in each direction.
You can do everything you want with a small set of commands.
An open ended interface that can be efficiently virtualized.
Or why not just implement something like 9p?
> i respond to this because i think there is a prevalent
> attitude, not well-informed by experience, that hardware
> is bad and impossible to program. my opinion, based on
> experience, is this is not true. and restating the untruth
> has the consequence of discouraging folk from working
> on drivers, thus reenforcing the myth.
Sorry, my experience does not match yours. May be things have
improved since I used to write drivers but controllers like
NEC765 were pretty bad (I can cite a lot of other examples
but I won't, not here!).
As a driver writer one should go in with eyes open so nothing
grosses you out, read specs thoroughly but when in doubt
experiment and so on.
> were it true, it would not be an attitude condusive
> to getting things done.
If only. Unfortunately too much bad hardware gets drivers
written for them.
This is so far from qemu or plan9 that I will stop now.
next prev parent reply other threads:[~2008-06-15 0:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 0:39 erik quanstrom
2008-06-14 1:24 ` Bakul Shah
2008-06-14 4:58 ` Bruce Ellis
2008-06-14 5:30 ` Iruata Souza
2008-06-14 12:53 ` erik quanstrom
2008-06-14 15:14 ` Iruata Souza
2008-06-14 14:15 ` erik quanstrom
2008-06-15 0:01 ` Bakul Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-13 1:54 Venkatesh Srinivas
2008-06-13 2:01 ` Pietro Gagliardi
2008-06-13 3:38 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 3:38 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 4:00 ` Venkatesh Srinivas
2008-06-13 8:08 ` sqweek
2008-06-13 10:41 ` Bruce Ellis
2008-06-13 11:47 ` Rodolfo kix García
2008-06-13 19:05 ` Bakul Shah
2008-06-13 20:03 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 20:33 ` Charles Forsyth
2008-06-13 20:30 ` erik quanstrom
2008-06-13 20:58 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52 ` erik quanstrom
2008-06-14 0:40 ` Bakul Shah
2008-06-13 20:35 ` Charles Forsyth
2008-06-13 23:01 ` Bakul Shah
2008-06-13 23:26 ` Pietro Gagliardi
2008-06-13 23:36 ` Bakul Shah
2008-06-13 23:42 ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52 ` Uriel
2008-06-17 10:51 ` matt
2008-06-13 12:57 ` stefanha
2008-06-13 12:22 ` Fazlul Shahriar
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=20080615000130.87BDA5B5B@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--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).