diff options
author | Tom Tucker <tom@opengridcomputing.com> | 2007-12-30 21:07:36 -0600 |
---|---|---|
committer | J. Bruce Fields <bfields@citi.umich.edu> | 2008-02-01 16:42:08 -0500 |
commit | 38a417cc993f4535548e47207f9894e7c27e05e4 (patch) | |
tree | f8035bcf6bc9a4831b152f5556b14cb3b48a72b8 /net/xfrm | |
parent | d7979ae4a050a45b78af51832475001b68263d2a (diff) | |
download | blackbird-op-linux-38a417cc993f4535548e47207f9894e7c27e05e4.tar.gz blackbird-op-linux-38a417cc993f4535548e47207f9894e7c27e05e4.zip |
svc: Add xpo_accept transport function
Previously, the accept logic looked into the socket state to determine
whether to call accept or recv when data-ready was indicated on an endpoint.
Since some transports don't use sockets, this logic now uses a flag
bit (SK_LISTENER) to identify listening endpoints. A transport function
(xpo_accept) allows each transport to define its own accept processing.
A transport's initialization logic is reponsible for setting the
SK_LISTENER bit. I didn't see any way to do this in transport independent
logic since the passive side of a UDP connection doesn't listen and
always recv's.
In the svc_recv function, if the SK_LISTENER bit is set, the transport
xpo_accept function is called to handle accept processing.
Note that all functions are defined even if they don't make sense
for a given transport. For example, accept doesn't mean anything for
UDP. The function is defined anyway and bug checks if called. The
UDP transport should never set the SK_LISTENER bit.
Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
Acked-by: Neil Brown <neilb@suse.de>
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Greg Banks <gnb@sgi.com>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'net/xfrm')
0 files changed, 0 insertions, 0 deletions