DragonFly kernel List (threaded) for 2008-08
Re: [netmp] socket accesses
:I'm not sure what the protocol thread would have to do in this case. Isn't it
:enough to just have it set the relevant flag in response to the message?
I greped through all the uses of SS_CANTRCVMORE. Nearly all uses
are on the user side and not on the protocol side. In fact, the
only protocol-side use, other then setting the flag and waking up
any blocked readers, is in the TCP stack where it looks like it
simply uses the flag to determine whether to append new mbufs onto
the sockbuf or to simply free them.
It looks to me that the user side can just set the flag w/ an atomic
Another alternative is to create a user-side flag set and a protocol-side
flag set, so userland can set flags without using atomic instructions,
and the protocol side would check both flags (A|B). That seems more