Re: Dupping message data

i haven't been following this discussion.... so i may be
talking gibberish here but...

i've done ports of various versions of BSD tcp/ip code to
realtime OS'es (e.g. VxWorks, my own little exec).
the way i usually go about doing things is to have one thread
that provide context for all network related things.
it'll service a queue. when there are "networking" things
to do i enqueue jobs to this queue. network thread just
services each item as it gets chances to run.

network interrupts are ack'ed pretty much immediately and
bulk of the real work handling those interrupts (reading
data, etc.) is done in the context of this thread.

it's possible to have a thread for different things (e.g.
fior each of the network devices, each protocol, etc.)
but things usually work pretty well with just one thread.

there are some places in the bsd code that are not thread-safe --
these have to be fixed up -- and/or kludged around via
big mutex blocks... ;-)

hwajin
Received on Wed Oct 13 10:55:18 1993