>> I imagine the kernel must store this info somewhere since it has to
>> deliver packets to said process - I guess via the descriptor
>> table[s].

> The kernel doesn't store this information, because it doesn't need it
> during normal operation.  The kernel doesn't deliver the packets to a
> process.  The packets get "delivered" to a socketbuffer which hangs
> [off] the vnode.  The first process to read from that vnode [gets]
> the requested packets.

Well, there does have to be _some_ link between the two, because a
process that's blocked in a read or recvfrom on that socket will be
awakened by arriving data.  But that's probably not useful, because the
only link between the two is (probably - I haven't specifically looked)
a sleep/wakeup location pair, which if you wanted to take advatange of
it would require walking the sleeping process chains.  Probably easier
to scan the open file tables.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     01 EE 31 F6 BB 0C 34 36  00 F3 7C 5A C1 A0 67 1D