Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
rxrpc: Don't use a ring buffer for call Tx queue
Change the way the Tx queueing works to achieve the following ends: (1) The filling of packets, the encryption of packets and the transmission of packets can be handled in parallel by separate threads, rather than sendmsg() allocating, filling, encrypting and transmitting each packet before moving onto the next one. (2) Get rid of a fixed size ring which sets a hard limit on the number of packets that can be retained in the ring. This allows the number of packets to increase without having to allocate a very large ring or having variable-sized rings. (3) Allow the filler/encrypter to run ahead of the transmission window. (4) Make it easier to do zero copy UDP from the packet buffers. (5) Make it easier to do zero copy from userspace to the packet buffers - and thence to UDP. To that end, the following changes are made: (1) Create a new struct, rxrpc_txbuf, to use instead of sk_buff for this. This contains the packet header and data bufferage aligned so that crypto is correctly aligned. (2) Keep the transmissable packets in a linked list on the call struct rather than in a ring. As a consequence the annotation buffer isn't used either; rather a flag is set on the packet to indicate ackedness. (3)
- Loading branch information
Showing
16 changed files
with
538 additions
and
533 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.