Re: comm_*_incoming changes

From: Duane Wessels <wessels@dont-contact.us>
Date: Wed, 27 May 1998 20:57:52 -0600

Stewart Forster writes:

>
> I'm slightly confused by the wording of the description. For

Sorry, I got the numbers wrong. It should be:

# TAG: incoming_min_rate
# TAG: incoming_max_rate
# These specify how often the "incoming" sockets should be
# checked, compared with established connections. Note, the
# "incoming" sockets are where we accept new HTTP connections and
# where we process ICP queries.
#
# If there was just activity on an incoming socket, then we will
# check the incoming sockets again after processing the next
# 'incoming_max_rate' I/O events. If there was not any recent
# incoming activity, we check incoming sockets again after
# processing the next 'incoming_min_rate' I/O events.
#
#incoming_min_rate 16
#incoming_max_rate 2

If there was just I/O, we wait 2 more I/O events and check
incoming again.

If there is no incoming I/O, we check every 16 I/O events.

I don't like 'rate' either.

Duane W.
Received on Tue Jul 29 2003 - 13:15:50 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:47 MST