On May 1, 2007, at 1:26 PM, Anders Persson wrote:
Spencer Shepler wrote:
The kernel RPC interfaces use the streams timer mechanism to
timeout and close idle connections; again, a nice to have
but not a hard requirement.
So far there have been not plans for adding any timer mechanism to
the interface itself. The user would
have to rely on timeout(9F) for that functionality.
That's fine.
I should also mention that the
NFS server changes the receive buffer size/window size to
stop-down the client when it is not receiving data as quickly
as it is sending requests. Seems like that will be covered
with what you propose.
Yes, you will be able to modify the buffer size via ksock_setsockopt
().
Finally, what additional thoughts do you have about the
event notification mechanism. Will it deliver multiple
events, simultaneously for a particular socket?
That is the current design; there is no mechanism in the interface
that synchronize the events, however, at least for TCP, I suppose
that those scenarios would be uncommon since squeues should ensure
synchronization.
Or will
it wait for one event delivery to be complete before
delivering the next. Would it be possible chain or provide
a list of events?
It could be possible, but the consumer can have this type of
behavior by adding some additional logic to the callback functions.
So for that reason I do not think the additional complexity is needed.
Agreed.
Spencer
_______________________________________________
networking-discuss mailing list
[email protected]
