From: Pete Zaitcev <zaitcev@redhat.com>
To: Sergej Pupykin <ps@lx-ltd.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB: count of reading urbs
Date: Fri, 21 Jul 2006 22:17:45 -0700 [thread overview]
Message-ID: <20060721221745.62349077.zaitcev@redhat.com> (raw)
In-Reply-To: <mailman.1153399921.28044.linux-kernel2news@redhat.com>
On 20 Jul 2006 16:43:23 +0400, Sergej Pupykin <ps@lx-ltd.ru> wrote:
> Please, tell me. If I submit one urb, can I lost data? (If data comes when
> urb callback executed)
USB by its nature requires devices to have some buffering, because
polling by the host may be irregular or not often enough. So, usually
there is no loss of data in such case. If you delay resubmissions
enough to overrun device's internal queue, it may happen.
-- Pete
next parent reply other threads:[~2006-07-22 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1153399921.28044.linux-kernel2news@redhat.com>
2006-07-22 5:17 ` Pete Zaitcev [this message]
2006-07-20 12:43 USB: count of reading urbs Sergej Pupykin
2006-07-20 22:21 ` Greg KH
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=20060721221745.62349077.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ps@lx-ltd.ru \
/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