diff options
author | Ying Xue <ying.xue@windriver.com> | 2013-01-20 23:30:09 +0100 |
---|---|---|
committer | Paul Gortmaker <paul.gortmaker@windriver.com> | 2013-02-15 17:01:58 -0500 |
commit | aba79f332f46ca8529f3e62a9fc2926c8fe75e44 (patch) | |
tree | bd22bd59d69f28e71f075912ec024082adf5a36a /README | |
parent | 57467e56293796f780e91a24600a732516f534ac (diff) | |
download | linux-aba79f332f46ca8529f3e62a9fc2926c8fe75e44.tar.bz2 |
tipc: byte-based overload control on socket receive queue
Change overload control to be purely byte-based, using
sk->sk_rmem_alloc as byte counter, and compare it to a calculated
upper limit for the socket receive queue.
For all connection messages, irrespective of message importance,
the overload limit is set to a constant value (i.e, 67MB). This
limit should normally never be reached because of the lower
limit used by the flow control algorithm, and is there only
as a last resort in case a faulty peer doesn't respect the send
window limit.
For datagram messages, message importance is taken into account
when calculating the overload limit. The calculation is based
on sk->sk_rcvbuf, and is hence configurable via the socket option
SO_RCVBUF.
Cc: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions