From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Busy mouse WAS: Re: Making read(1) an rc(1) builtin?
Date: Sat, 9 Apr 2011 12:26:02 +0000 [thread overview]
Message-ID: <86ei5behlx.fsf@cmarib.ramside> (raw)
In-Reply-To: <e8a0c97b996aaea2080b1f845c3c7a0d@ladd.quanstro.net> (erik quanstrom's message of "Thu, 7 Apr 2011 16:19:06 -0400")
erik quanstrom <quanstro@quanstro.net> writes:
> i ran some actual tests, and it turns out that i can get
> 1515 interrupts/sec and 1950 syscalls/sec just by moving my
It occurs to me that these values are in the audible range for human
hearing. How cool would it be to have something like "stats -a"
generate an audible version of system stats?!
> usb mouse constantly. the load average is still 0, and the
> interrupt time is <= 3%
My load is also close to zero, when just moving the mouse. If, for
example, I do a "du -a" in an Acme "win" window, the mouse disappears
and/or becomes unusuably slow until Acme finishes.
Acme also hangs for me while retrieving files and directory listings on
/n/sources. Although the mouse remains responsive during that time,
Acme becomes unresponsive... not even selecting text with the button1
works.
> the mouse, the i would think that the fact that your machine
> is doing 8259-style interrupts has something to do with it.
No hablo 8259. ??
--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-04-09 12:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 22:30 [9fans] " smiley at zenzebra.mv.com
2011-04-03 23:22 ` pmarin
2011-04-03 23:41 ` Tristan Plumb
2011-04-04 2:02 ` Ethan Grammatikidis
2011-04-04 2:53 ` erik quanstrom
2011-04-04 7:54 ` Tristan Plumb
2011-04-04 9:26 ` roger peppe
2011-04-04 21:35 ` smiley
2011-04-04 21:46 ` Anthony Sorace
2011-04-04 22:03 ` erik quanstrom
2011-04-05 8:57 ` Balwinder S Dheeman
2011-04-04 22:00 ` Oleg Finkelshteyn
2011-04-04 22:33 ` erik quanstrom
2011-04-04 23:01 ` Lyndon Nerenberg
2011-04-05 8:58 ` yy
2011-04-05 19:54 ` Ethan Grammatikidis
2011-04-05 19:56 ` erik quanstrom
2011-04-05 20:54 ` Ethan Grammatikidis
2011-04-05 21:53 ` andrey mirtchovski
2011-04-06 16:32 ` Bakul Shah
2011-04-06 16:43 ` roger peppe
2011-04-06 18:15 ` erik quanstrom
2011-04-06 18:37 ` Yaroslav
2011-04-07 8:45 ` Greg Comeau
2011-04-06 18:18 ` erik quanstrom
2011-04-07 8:45 ` Greg Comeau
2011-04-05 9:10 ` roger peppe
2011-04-05 15:47 ` ron minnich
2011-04-05 15:52 ` Jacob Todd
2011-04-05 15:57 ` erik quanstrom
2011-04-05 16:04 ` Rudolf Sykora
2011-04-05 17:17 ` ron minnich
2011-04-05 17:49 ` smiley
2011-04-05 18:01 ` erik quanstrom
2011-04-05 19:50 ` Yaroslav
2011-04-06 15:27 ` smiley
2011-04-06 15:32 ` Jacob Todd
2011-04-07 1:26 ` [9fans] Busy mouse WAS: " smiley
2011-04-07 11:49 ` erik quanstrom
2011-04-07 19:59 ` smiley
2011-04-07 20:19 ` erik quanstrom
2011-04-09 12:26 ` smiley [this message]
2011-04-09 12:33 ` erik quanstrom
2011-04-05 16:28 ` [9fans] " dexen deVries
2011-04-05 17:05 ` Bakul Shah
2011-04-03 23:51 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-04-04 3:01 ` 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=86ei5behlx.fsf@cmarib.ramside \
--to=smiley@zenzebra.mv.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).