HP3000-L Archives

April 2001, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Emerson <[log in to unmask]>
Reply To:
Tom Emerson <[log in to unmask]>
Date:
Mon, 30 Apr 2001 12:26:25 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
On Fri, 27 Apr 2001 16:18:35 -0700, Gavin Scott <[log in to unmask]> wrote:

>Tom after me:
>> >One question would be why are you using soft interrupts in the
>> first place rather than just having one IOWAIT or HPSELECT that
>> waits on all your input sources at the same time so that
>> interrupts aren't really needed.
>>
>> The reason was inferred by the closing BTW comment: this program handles
>> both (berkeley) socket I/O and message file I/O.
>
>If you replaced the Berkeley sockets interface with NetIPC, then you could
>use one IOWAIT for all your asynchronous I/O.

I'll have to file this "for future reference" -- it's a bit late in this
project to switch now :)  Seriously, though, I was unaware that NetIPC
would bring the sockets into the "IOWAIT" call [I suppose HP should have
implemented sockets this way then cleverly changed the "select()" call into
a wrapper for IOWAIT and nobody would be the wiser...]

>Maybe not an *easy* solution, but the "MPE way" to do this sort of thing.

It has been quite some time since I looked at NetIPC -- had HP's documents
been a little clearer, I might have started with that.  As it turns out,
there are a wealth of Unix/Linux books & manuals out there that
cover "sockets" programming, but none (other than HP's own manual) for
NetIPC.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2