/linux/include/linux/sunrpc/ |
H A D | sched.h | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
H A D | xprt.h | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
/linux/net/sunrpc/ |
H A D | sched.c | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
H A D | xprt.c | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
H A D | clnt.c | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
H A D | xprtsock.c | diff 02107148349f31eee7c0fb06fd7a880df73dbd20 Tue Jan 03 09:55:49 CET 2006 Chuck Lever <cel@netapp.com> SUNRPC: switchable buffer allocation
Add RPC client transport switch support for replacing buffer management on a per-transport basis.
In the current IPv4 socket transport implementation, RPC buffers are allocated as needed for each RPC message that is sent. Some transport implementations may choose to use pre-allocated buffers for encoding, sending, receiving, and unmarshalling RPC messages, however. For transports capable of direct data placement, the buffers can be carved out of a pre-registered area of memory rather than from a slab cache.
Test-plan: Millions of fsx operations. Performance characterization with "sio" and "iozone". Use oprofile and other tools to look for significant regression in CPU utilization.
Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|