From: Dan Cross <crossd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] new usb stack and implicit timeouts
Date: Mon, 20 Jul 2009 15:51:06 -0400 [thread overview]
Message-ID: <aa7e41150907201251u10df3548q569b179d7b6f684@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.00.0907201209010.25656@legolas.orthanc.ca>
fd = open("/some/ctl", OWRITE);
write(fd, "timeout LONG_ENOUGH", length);
close(fd);
On Mon, Jul 20, 2009 at 2:10 PM, Lyndon Nerenberg<lyndon@orthanc.ca> wrote:
>> I am unsure I would remove timeouts even from bulk endpoints.
>> It is true that some devices (the usb/serial for example) need to
>> read for an undefined time waiting for data, but I don't think that is
>> an issue as long
>> as the timeouts are long enough,
>
> Please show us the algorithm that *correctly* determines 'long enough' for
> every application talking to the devices.
>
>
next prev parent reply other threads:[~2009-07-20 19:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 7:16 cinap_lenrek
2009-07-19 7:21 ` Bruce Ellis
2009-07-19 7:54 ` cinap_lenrek
2009-07-19 9:07 ` Francisco J Ballesteros
2009-07-19 11:05 ` Richard Miller
2009-07-19 11:30 ` Francisco J Ballesteros
2009-07-19 11:51 ` Richard Miller
2009-07-19 11:56 ` Francisco J Ballesteros
2009-07-19 13:40 ` erik quanstrom
2009-07-19 13:53 ` erik quanstrom
2009-07-19 14:03 ` Richard Miller
2009-07-19 14:32 ` erik quanstrom
2009-07-19 15:14 ` Francisco J Ballesteros
2009-07-19 15:46 ` cinap_lenrek
2009-07-19 15:58 ` Francisco J Ballesteros
2009-07-20 7:12 ` Gorka Guardiola
2009-07-20 15:07 ` Dan Cross
2009-07-20 16:25 ` Francisco J Ballesteros
2009-07-20 18:10 ` Lyndon Nerenberg
2009-07-20 19:51 ` Dan Cross [this message]
2009-07-21 8:51 ` Francisco J Ballesteros
2009-07-19 15:36 ` Richard Miller
2009-07-19 11:41 ` Charles Forsyth
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=aa7e41150907201251u10df3548q569b179d7b6f684@mail.gmail.com \
--to=crossd@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).