Sean Hefty [Tue, 5 Mar 2013 21:39:00 +0000 (13:39 -0800)]
librdmacm/rstream: Adjust transfer counts
A customer has reported that 100 transfers for large sizes
is insufficient to achieve the top bandwidth over a high
latency link. Contrary, 100,000 transfers is too high for
small latency ping-pong over a slow connection.
Sean Hefty [Tue, 5 Mar 2013 21:39:00 +0000 (13:39 -0800)]
librdmacm/rstream: Adjust transfer counts
A customer has reported that 100 transfers for large sizes
is insufficient to achieve the top bandwidth over a high
latency link. Contrary, 100,000 transfers is too high for
small latency ping-pong over a slow connection.
Sean Hefty [Tue, 5 Mar 2013 21:39:00 +0000 (13:39 -0800)]
librdmacm/rstream: Adjust transfer counts
A customer has reported that 100 transfers for large sizes
is insufficient to achieve the top bandwidth over a high
latency link. Contrary, 100,000 transfers is too high for
small latency ping-pong over a slow connection.
Sean Hefty [Tue, 5 Mar 2013 21:39:00 +0000 (13:39 -0800)]
librdmacm/rstream: Adjust transfer counts
A customer has reported that 100 transfers for large sizes
is insufficient to achieve the top bandwidth over a high
latency link. Contrary, 100,000 transfers is too high for
small latency ping-pong over a slow connection.
Sean Hefty [Wed, 20 Feb 2013 04:03:58 +0000 (20:03 -0800)]
librdmacm/rsocket: Fix resetting O_NONBLOCK after calling shutdown
Shutdown switches an rsocket from nonblocking to blocking to
ensure that all data has been sent. After completing all
transfers, it should switch back to nonblocking; this handles
partial shutdown situations, where only half the connection
is shut down. However, the code uses the value of '1' to
set the nonblocking flag, rather than O_NONBLOCK. Fix this.
Sean Hefty [Wed, 20 Feb 2013 04:03:58 +0000 (20:03 -0800)]
rsocket: Fix resetting O_NONBLOCK after calling shutdown
Shutdown switches an rsocket from nonblocking to blocking to
ensure that all data has been sent. After completing all
transfers, it should switch back to nonblocking; this handles
partial shutdown situations, where only half the connection
is shut down. However, the code uses the value of '1' to
set the nonblocking flag, rather than O_NONBLOCK. Fix this.
Sean Hefty [Wed, 20 Feb 2013 04:03:58 +0000 (20:03 -0800)]
rsocket: Fix resetting O_NONBLOCK after calling shutdown
Shutdown switches an rsocket from nonblocking to blocking to
ensure that all data has been sent. After completing all
transfers, it should switch back to nonblocking; this handles
partial shutdown situations, where only half the connection
is shut down. However, the code uses the value of '1' to
set the nonblocking flag, rather than O_NONBLOCK. Fix this.