[SCTP]: Rewrite of sctp buffer management code
This patch introduces autotuning to the sctp buffer management code similar to the TCP. The buffer space can be grown if the advertised receive window still has room. This might happen if small message sizes are used, which is common in telecom environmens. New tunables are introduced that provide limits to buffer growth and memory pressure is entered if to much buffer spaces is used. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
13c99b248f
commit
4d93df0abd
@@ -685,6 +685,24 @@ struct sctp_ulpevent *sctp_ulpevent_make_rcvmsg(struct sctp_association *asoc,
|
||||
struct sctp_ulpevent *event = NULL;
|
||||
struct sk_buff *skb;
|
||||
size_t padding, len;
|
||||
int rx_count;
|
||||
|
||||
/*
|
||||
* check to see if we need to make space for this
|
||||
* new skb, expand the rcvbuffer if needed, or drop
|
||||
* the frame
|
||||
*/
|
||||
if (asoc->ep->rcvbuf_policy)
|
||||
rx_count = atomic_read(&asoc->rmem_alloc);
|
||||
else
|
||||
rx_count = atomic_read(&asoc->base.sk->sk_rmem_alloc);
|
||||
|
||||
if (rx_count >= asoc->base.sk->sk_rcvbuf) {
|
||||
|
||||
if ((asoc->base.sk->sk_userlocks & SOCK_RCVBUF_LOCK) ||
|
||||
(!sk_stream_rmem_schedule(asoc->base.sk, chunk->skb)))
|
||||
goto fail;
|
||||
}
|
||||
|
||||
/* Clone the original skb, sharing the data. */
|
||||
skb = skb_clone(chunk->skb, gfp);
|
||||
|
Reference in New Issue
Block a user