From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: mark gross <mgross@linux.intel.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Real time USB2Serial devices and behaivor
Date: Wed, 26 Mar 2008 21:13:06 -0700 [thread overview]
Message-ID: <20080327041306.GA10095@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803262255320.21714-100000@netrider.rowland.org>
On Wed, Mar 26, 2008 at 10:58:37PM -0400, Alan Stern wrote:
> On Wed, 26 Mar 2008, Greg KH wrote:
>
> > > Is there any reason to think that if I created my own isochronous
> > > USB2Serial adapter and iso-usb-driver that I couldn't get determinism?
> >
> > I strongly doubt it as others have tried and failed in the past.
>
> I don't understand. Isochronous transfers have pretty strict
> transfer-time guarantees. Why wouldn't this work?
I don't know, but the person who tried this a while ago said it wasn't
really "real-time" enough for their application (robot arm movement).
> One reason I can think of is that Iso transfers aren't reliable. But
> then regular RS232-type serial transfers aren't reliable either.
>
> The only other reason is that the USB stack itself has an unpredictable
> amount of overhead. However I think it should fall within an
> acceptable range for RT applications.
It's all about bounding the longest latency. Sometimes, under heavy
loads, latency can be pretty big. But now that we have the -rt kernel,
it might be a lot better than before, so that might be possible now,
haven't tried it...
good luck,
greg k-h
next prev parent reply other threads:[~2008-03-27 4:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 15:25 Real time USB2Serial devices and behaivor mark gross
2008-03-26 16:27 ` Greg KH
2008-03-26 16:49 ` mark gross
2008-03-26 23:24 ` Greg KH
2008-03-27 2:58 ` Alan Stern
2008-03-27 4:13 ` Greg KH [this message]
2008-03-27 19:48 ` David Brownell
2008-03-27 21:00 ` Lennart Sorensen
2008-03-27 21:08 ` David Brownell
2008-03-28 13:38 ` Lennart Sorensen
2008-04-03 14:26 ` Ming Lei
2008-04-03 14:45 ` Peter Zijlstra
2008-04-03 15:52 ` Greg KH
2008-04-03 6:24 ` Jon Masters
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=20080327041306.GA10095@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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