Searched hist:"78147 ca8" (Results 1 – 6 of 6) sorted by relevance
/openbmc/linux/include/linux/sunrpc/ |
H A D | svc_rdma_pcl.h | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|
H A D | svc_rdma.h | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|
/openbmc/linux/net/sunrpc/xprtrdma/ |
H A D | svc_rdma_pcl.c | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|
H A D | Makefile | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|
H A D | svc_rdma_recvfrom.c | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|
/openbmc/linux/include/trace/events/ |
H A D | rpcrdma.h | 78147ca8 Mon Jun 22 09:15:41 CDT 2020 Chuck Lever <chuck.lever@oracle.com> svcrdma: Add a "parsed chunk list" data structure
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client.
There are several benefits to this small additional overhead:
* It enables support for more than one chunk in incoming Read and Write lists.
* It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol.
* It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer.
Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
|