From: Patrick Maupin <pmaupin@gmail.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Wed, 14 Mar 2012 13:13:49 -0500 [thread overview]
Message-ID: <CAPz3yKc96S8GqeGMVa1z35=w4zb9X_HmNypwz6GVNGbVdJ0D6g@mail.gmail.com> (raw)
In-Reply-To: <20120314104920.697EA40617@snark.thyrsus.com>
On Wed, Mar 14, 2012 at 5:49 AM, Eric S. Raymond <esr@thyrsus.com> wrote:
> Since the Plane Jane design concept depends on the host system being
> able to see USB events corresponding to serial handshaking state
> changes, I went looking for information on which handshake signals
> from which serial-to-USB adapters actually propagate these signals
> through. I focused on Linux becase that's the kernel for the
> bufferbloat deployment.
There is another question, which is about the internal latency inside
the USB adapter. In general (e.g. for character data) the USB
adapters will deliberately add some latency so as to make better use
of internal buffering resources. (Once an adapter sends a packet of
characters up to the host, it has to wait for an ACK before it can
reuse that buffer -- it might need to resend for a NAK.) So if the
host polls with an interrupt packet, and there is data at the USB
device but it reasonably expects that more data is coming, it might
not send the packet up right away.
The FTDI devices have a latency timer that allows you to control this
somewhat. But even better, if we're going to use the PPS signal, they
essentially guarantee that they will send ASAP on modem control signal
change. We might need to characterize "ASAP" but I would hope that it
doesn't vary too much.
I know nothing about the Prolific device; you might look for what they
have to say about latency.
next prev parent reply other threads:[~2012-03-14 18:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 10:49 Eric S. Raymond
2012-03-14 12:55 ` Ron Frazier (NTP)
2012-03-14 12:58 ` Ron Frazier (NTP)
2012-03-14 18:13 ` Patrick Maupin [this message]
2012-03-14 18:42 ` Eric S. Raymond
2012-03-14 18:57 ` Dave Taht
2012-03-14 20:09 ` Patrick Maupin
2012-03-15 3:33 ` Patrick Maupin
2012-03-15 4:23 ` Eric S. Raymond
[not found] <CAFv7OigTLhw24i+jRshv0YgLogyx_GEREAOkP7tieeH1Nr5WzA@mail.gmail.com>
2012-03-15 14:37 ` tz
2012-03-15 14:52 ` Ron Frazier (NTP)
2012-03-15 17:57 ` Eric S. Raymond
2012-03-15 18:31 ` Eric S. Raymond
2012-03-15 18:54 ` Patrick Maupin
2012-03-15 19:36 ` Eric S. Raymond
2012-03-15 19:55 ` Patrick Maupin
2012-03-15 19:14 ` tz
2012-03-15 19:50 ` Eric S. Raymond
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='CAPz3yKc96S8GqeGMVa1z35=w4zb9X_HmNypwz6GVNGbVdJ0D6g@mail.gmail.com' \
--to=pmaupin@gmail.com \
--cc=esr@thyrsus.com \
--cc=thumbgps-devel@lists.bufferbloat.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