diff options
author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2008-04-17 18:52:19 -0400 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2008-04-19 16:52:44 -0400 |
commit | b6ddf64ffe9d59577a9176856bb6fe69a539f573 (patch) | |
tree | dd12c31555cf9449dd6094428d377186b3c4c373 /lib/kobject.c | |
parent | 24b74bf0c9e08cbda74d3c64af69ad402ed54e04 (diff) | |
download | kernel-crypto-b6ddf64ffe9d59577a9176856bb6fe69a539f573.tar.gz kernel-crypto-b6ddf64ffe9d59577a9176856bb6fe69a539f573.tar.xz kernel-crypto-b6ddf64ffe9d59577a9176856bb6fe69a539f573.zip |
SUNRPC: Fix up xprt_write_space()
The rest of the networking layer uses SOCK_ASYNC_NOSPACE to signal whether
or not we have someone waiting for buffer memory. Convert the SUNRPC layer
to use the same idiom.
Remove the unlikely()s in xs_udp_write_space and xs_tcp_write_space. In
fact, the most common case will be that there is nobody waiting for buffer
space.
SOCK_NOSPACE is there to tell the TCP layer whether or not the cwnd was
limited by the application window. Ensure that we follow the same idiom as
the rest of the networking layer here too.
Finally, ensure that we clear SOCK_ASYNC_NOSPACE once we wake up, so that
write_space() doesn't keep waking things up on xprt->pending.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'lib/kobject.c')
0 files changed, 0 insertions, 0 deletions