9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Digby Tarvin <digbyt@acm.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A shot in the dark
Date: Wed, 28 May 2008 01:06:42 +0100	[thread overview]
Message-ID: <20080528000641.GA2649@skaro.cthulhu.dircon.co.uk> (raw)
In-Reply-To: <B45F20FF-0EFB-4AD2-9509-B416CD57B93A@mac.com>

Don't know where to find that paper, but it reminds of a friend
at UNSW (in Sydney) that used to instrument the OS9 kernel by setting
and clearing bits in the parallel port.

The monitoring hardware was indeed simple - an analogue voltmeter
connected to the bit of interest to produce a simple but effective
short term average.

For example, a bit that is cleared when in the system idle loop
produced a 'tacho' style analogue load meter.

That must have been in the early 80's, but I still find the parallel
interface a good method of getting real-time diagnostics, or front
panel style indicators for statuses such as system/user mode.
Consequently I don't welcome the current trend toward optimising
them out of new hardware. USB parallel interfaces may be ok for
driving printers, but they are no substitute if you want a very low
overhead, low latency i/o mechanism.

Regards,
DigbyT

On Tue, May 27, 2008 at 06:54:58PM -0400, Pietro Gagliardi wrote:
> No, I wasn't around that time :-) But I was looking for the Hello
> World X11 paper a while back, which was pre-website USENIX. But on the
> USENIX website it seems that you can purchase papers from before
> 1991(?). Perhaps they had a paper?
>
> On May 27, 2008, at 6:02 PM, ron minnich wrote:
>
> >OK, this is a long shot, but i'm running out of ideas.
> >
> >Long, long ago, at a Usenix, I saw a talk by some adventurous
> >australians (are there any other kind?). It was concerning some neat
> >hardware designed for kernel monitoring.
> >
> >They had done a very neat hack. Basically, they modified the C
> >compiler so that, on function entry and exit, the code would emit a
> >16-bit quantity to the parallel port. They had some simple hardware to
> >grab the data.
> >
> >WIth this, they were able to get some nice kernel performance numbers,
> >all for the (low at the time) cost of an outw to the parallel port.
> >
> >OK, I have done some searching and can't find this. IIRC it was
> >pre-website usenix. I am going to UCB this week and may have time to
> >hunt it down in the paper archives, but ... just wondering ... anyone
> >else remember this?
> >
> >thanks
> >
> >ron
> >
>

--
Digby R. S. Tarvin                                          digbyt(at)digbyt.com
http://www.digbyt.com



  parent reply	other threads:[~2008-05-28  0:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 22:02 ron minnich
2008-05-27 22:54 ` Pietro Gagliardi
2008-05-27 23:00   ` ron minnich
2008-05-28  0:06   ` Digby Tarvin [this message]
2008-05-28  2:54     ` Paul Lalonde
2008-05-28  7:31       ` Bruce Ellis
2008-05-28 15:49         ` Digby Tarvin
2008-05-28 18:34         ` [9fans] OT: supporting multiple VGA cards (was "A shot in the dark") Digby Tarvin
2008-05-28 19:07           ` ron minnich
2008-05-28  0:16 ` [9fans] A shot in the dark Bakul Shah
2008-05-28  0:30   ` ron minnich
2008-05-28  7:17     ` Bruce Ellis
2008-05-28 15:53       ` Digby Tarvin

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=20080528000641.GA2649@skaro.cthulhu.dircon.co.uk \
    --to=digbyt@acm.org \
    --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).