Searched hist:"50 f484e2" (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/net/sunrpc/xprtrdma/ |
| H A D | svc_rdma_backchannel.c | 50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
|
| H A D | transport.c | 50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
|
| /openbmc/linux/include/linux/sunrpc/ |
| H A D | xprt.h | 50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
|
| /openbmc/linux/net/sunrpc/ |
| H A D | xprt.c | 50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
|
| H A D | xprtsock.c | 50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
50f484e2 Thu Aug 30 12:27:29 CDT 2018 Trond Myklebust <trond.myklebust@hammerspace.com> SUNRPC: Treat the task and request as separate in the xprt_ops->send_request()
When we shift to using the transmit queue, then the task that holds the
write lock will not necessarily be the same as the one being transmitted.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
|