From: Chris Stankevitz <chrisstankevitz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Measuring USB "packet loss"
Date: Tue, 6 Nov 2012 12:07:32 -0800 [thread overview]
Message-ID: <CAPi0pstNUc7sXrZeDoxT9fH_tL11fGd6Bd-eQ-EoifsO6a20kA@mail.gmail.com> (raw)
Hello,
Some background: I'm running an experiment that is sensitive to USB
latency of a few milliseconds. During a typical overnight run I
encounter a handful such "latency events" and I am trying to
understand why they happen. If you can recommend kernel
settings/hacks that will decrease USB latency, please share!
===
Q: How can I retrieve a count of USB transmissions that failed or were
retransmitted? (analogous to ifconfig on ethernet)
Regarding this question:
a) Can you answer it?
b) Can you recommend something I can read that will answer it?
c) Can you recommend somewhere for me to ask this question where it
can be answered?
===
Thank you!
Chris
next reply other threads:[~2012-11-06 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 20:07 Chris Stankevitz [this message]
2012-11-06 22:51 ` [gentoo-user] Measuring USB "packet loss" James Cloos
2012-11-08 3:13 ` [gentoo-user] " Chris Stankevitz
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=CAPi0pstNUc7sXrZeDoxT9fH_tL11fGd6Bd-eQ-EoifsO6a20kA@mail.gmail.com \
--to=chrisstankevitz@gmail.com \
--cc=gentoo-user@lists.gentoo.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