From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] non-blocking IO
Date: Tue, 2 Jun 2020 10:22:12 +0200 [thread overview]
Message-ID: <46A39BDD-A854-40EF-B82A-176F1AB7B92E@planet.nl> (raw)
> > when you're working below the reliable stream level, you can't just do a > blocking 'read' for a packet; it pretty much has to be asynchronous
> Oh, you should look at the early BBN TCP for V6 Unix - they would have faced the same issue, with their TCP process. They did have the capac() call (which kind of alleviates the need for non-blocking I/O), but that may have only been available for ports/pipes; I'm not sure if the ARPANET device supported it.
I did. There is capac() support also for the IMP interface:
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr/imp11a.c
(see bottom two functions)
BBN took the same approach as Research: with capac() or select() one can prevent blocking on read() and write().
next reply other threads:[~2020-06-02 8:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 8:22 Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-06 13:29 Noel Chiappa
2020-06-02 20:13 Noel Chiappa
2020-06-02 20:43 ` Clem Cole
2020-06-02 22:14 ` Rich Morin
2020-06-03 16:31 ` Paul Winalski
2020-06-03 19:19 ` John P. Linderman
2020-06-02 14:19 Paul Ruizendaal
2020-06-02 17:45 ` Paul Winalski
2020-06-02 17:59 ` arnold
2020-06-02 18:53 ` Paul Winalski
2020-06-02 19:18 ` Clem Cole
2020-06-02 21:15 ` Lawrence Stewart
2020-06-02 18:23 ` Dan Cross
2020-06-02 18:56 ` Paul Winalski
2020-06-02 19:23 ` Clem Cole
2020-06-02 0:08 Noel Chiappa
2020-06-01 23:17 Noel Chiappa
2020-05-31 11:09 Paul Ruizendaal
2020-05-31 16:05 ` Clem Cole
2020-05-31 16:46 ` Warner Losh
2020-05-31 22:01 ` Rob Pike
2020-06-01 3:32 ` Dave Horsfall
2020-06-01 14:58 ` Larry McVoy
2020-06-04 9:04 ` Peter Jeremy
2020-06-04 14:19 ` Warner Losh
2020-06-04 16:34 ` Tony Finch
2020-06-04 16:50 ` Larry McVoy
2020-06-05 16:00 ` Dan Cross
2020-06-12 8:18 ` Dave Horsfall
2020-06-01 16:58 ` Heinz Lycklama
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=46A39BDD-A854-40EF-B82A-176F1AB7B92E@planet.nl \
--to=pnr@planet.nl \
--cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).