Re: [PATCH net-next 0/3] rxrpc: Tx length parameter

2017-06-08 Thread David Miller
From: David Howells Date: Wed, 07 Jun 2017 22:12:32 +0100 > Here's a set of patches that allows someone initiating a client call with > AF_RXRPC to indicate upfront the total amount of data that will be > transmitted. This will allow AF_RXRPC to encrypt directly from source > buffer to packet ra

[PATCH net-next 0/3] rxrpc: Tx length parameter

2017-06-07 Thread David Howells
Here's a set of patches that allows someone initiating a client call with AF_RXRPC to indicate upfront the total amount of data that will be transmitted. This will allow AF_RXRPC to encrypt directly from source buffer to packet rather than having to copy into the buffer and only encrypt when it's

Re: [PATCH net-next 0/3] rxrpc: Tx length parameter

2017-06-07 Thread David Howells
David Howells wrote: > (3) Introduce the RXRPC_TX_LENGTH cmsg. This can be provided on the first > sendmsg() that contributes data to a client call request or a service > call reply. If provided, the user must provide exactly that amount of > data or an error will be incurred.

[PATCH net-next 0/3] rxrpc: Tx length parameter

2017-06-07 Thread David Howells
Here's a set of patches that allows someone initiating a client call with AF_RXRPC to indicate upfront the total amount of data that will be transmitted. This will allow AF_RXRPC to encrypt directly from source buffer to packet rather than having to copy into the buffer and only encrypt when it's