From: Dan Parks <Dan.Parks@CAMotion.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Keystrokes, USB, and Latency
Date: 10 Feb 2003 15:05:22 -0500 [thread overview]
Message-ID: <1044907523.1438.475.camel@localhost> (raw)
I have a custom USB driver running in isochronous mode that timestamps
itself during it's operation to get statistical information. We have
succeeded in minimizing this number to the point that we can run it all
day under fairly high load, and it never miss a millisecond (it
communicates once a millisecond). However, if the user presses caps
lock, num lock, or scroll lock (everything else is ok), it ALWAYS misses
7-8 milliseconds. We are used to stripping down our computers to the
bare essential hardware/software, but this just seems bizarre, and after
extensive googling, I haven't seen anyone else complain about these
keystrokes interfering with gettimeofday() or causing excessive
latency. Any information would be appreciated.
Dan
next reply other threads:[~2003-02-10 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 20:05 Dan Parks [this message]
2003-02-10 22:16 ` Keystrokes, USB, and Latency Andries Brouwer
2003-02-11 15:28 ` anton wilson
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=1044907523.1438.475.camel@localhost \
--to=dan.parks@camotion.com \
--cc=linux-kernel@vger.kernel.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