rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs
Don't store the rxrpc protocol header in sk_buffs on the transmit queue,
but rather generate it on the fly and pass it to kernel_sendmsg() as a
separate iov. This reduces the amount of storage required.
Note that the security header is still stored in the sk_buff as it may get
encrypted along with the data (and doesn't change with each transmission).
Signed-off-by:
David Howells <dhowells@redhat.com>
Showing
- net/rxrpc/ar-internal.h 2 additions, 3 deletionsnet/rxrpc/ar-internal.h
- net/rxrpc/call_event.c 2 additions, 9 deletionsnet/rxrpc/call_event.c
- net/rxrpc/conn_object.c 0 additions, 1 deletionnet/rxrpc/conn_object.c
- net/rxrpc/output.c 56 additions, 27 deletionsnet/rxrpc/output.c
- net/rxrpc/rxkad.c 3 additions, 5 deletionsnet/rxrpc/rxkad.c
- net/rxrpc/sendmsg.c 8 additions, 43 deletionsnet/rxrpc/sendmsg.c
Loading
Please register or sign in to comment