Sean Hefty [Tue, 24 Jul 2012 21:13:55 +0000 (14:13 -0700)]
rspreload: Call init from getsockname()
netperf for some unknown reason calls getsockname() using a
hard coded value of 0, without first allocating a socket.
This causes the rsocket preload library to crash, since the
library has not been properly initialized.
Sean Hefty [Tue, 24 Jul 2012 18:40:10 +0000 (11:40 -0700)]
librspreload: Support server apps that call fork()
Provide limited support for applications that call fork(). To
handle fork(), we establish connections using normal sockets.
The socket is later converted to an rsocket when the user
makes the first call to a data transfer function (e.g. send,
recv, read, write, etc.).
Fork support is indicated by setting the environment variable
RDMAV_FORK_SAFE = 1. When set, the preload library will delay
converting to an rsocket until the user attemts to send or receive
data on the socket. To convert from a normal socket to an
rsocket, the preload library must inject a message on the
normal socket to synchronize between the client and server. As
a result, if the rsocket connection fails, the ability to
silently fallback to the normal socket may be compromised. Fork
support is disabled by default.
The current implementation works for simple test apps under
ideal conditions. Although it supports nonblocking sockets, it
uses blocking rsockets when migrating connections.
Sean Hefty [Tue, 24 Jul 2012 18:40:10 +0000 (11:40 -0700)]
librspreload: Support server apps that call fork()
Provide limited support for applications that call fork(). To
handle fork(), we establish connections using normal sockets.
The socket is later converted to an rsocket when the user
makes the first call to a data transfer function (e.g. send,
recv, read, write, etc.).
Fork support is indicated by setting the environment variable
RDMAV_FORK_SAFE = 1. When set, the preload library will delay
converting to an rsocket until the user attemts to send or receive
data on the socket. To convert from a normal socket to an
rsocket, the preload library must inject a message on the
normal socket to synchronize between the client and server. As
a result, if the rsocket connection fails, the ability to
silently fallback to the normal socket may be compromised. Fork
support is disabled by default.
The current implementation works for simple test apps under
ideal conditions. Although it supports nonblocking sockets, it
uses blocking rsockets when migrating connections.
Sean Hefty [Fri, 20 Jul 2012 00:09:29 +0000 (17:09 -0700)]
rspreload: Move fork handling to first data transfer
Instead of hooking fork and migrating the last accepted
connection to rsockets, perform the migration when the socket
first tries to send or receive data.
This is necessary to handle more complex cases of fork, where
the child process establishes connections.
Sean Hefty [Fri, 20 Jul 2012 00:09:29 +0000 (17:09 -0700)]
rspreload: Move fork handling to first data transfer
Instead of hooking fork and migrating the last accepted
connection to rsockets, perform the migration when the socket
first tries to send or receive data.
This is necessary to handle more complex cases of fork, where
the child process establishes connections.
Sean Hefty [Fri, 20 Jul 2012 00:09:29 +0000 (17:09 -0700)]
rspreload: Move fork handling to first data transfer
Instead of hooking fork and migrating the last accepted
connection to rsockets, perform the migration when the socket
first tries to send or receive data.
This is necessary to handle more complex cases of fork, where
the child process establishes connections.
Sean Hefty [Fri, 20 Jul 2012 00:09:29 +0000 (17:09 -0700)]
rspreload: Move fork handling to first data transfer
Instead of hooking fork and migrating the last accepted
connection to rsockets, perform the migration when the socket
first tries to send or receive data.
This is necessary to handle more complex cases of fork, where
the child process establishes connections.
Sean Hefty [Fri, 20 Jul 2012 00:09:29 +0000 (17:09 -0700)]
rspreload: Move fork handling to first data transfer
Instead of hooking fork and migrating the last accepted
connection to rsockets, perform the migration when the socket
first tries to send or receive data.
This is necessary to handle more complex cases of fork, where
the child process establishes connections.
projects / ~shefty / librdmacm.git / log