Dear developers, First, a shout-out. I'd like to say a big "Thank you!" for the work that you do supporting OpenAFS by addressing security vulnerabilities and ensuring that it continues to work on each newly-released version of (at least) Linux, Windows, and MacOS -- obviously the two most important goals for keeping OpenAFS moving forward.
However I have a plea: AFS has never noted as a real speed demon for data transfer. But its lack of performance is cited as a contributing factor leading some who might otherwise use AFS to consider alternatives (smb, nfs, cloud). In early 2019, Andrew Deason proposed some changes to RX which promised performance gains without changing to TCP. See <https://openafs-workshop.org/2019/schedule/how-to-saturate-a-10g-link-with-an-openafs-rx-fileserver/>. Andrew submitted patches to OpenAFS's gerrit primarily affecting sendmmsg and recvmmsg (circa gerrit ~13601 - 13613) but it's approaching two years later and from what I can tell, it doesn't look like these have made it into a released version yet. Can moving these changes forward to a released version of OpenAFS be prioritized? Removing "performance sucks," from the list of why sites may consider moving away from AFS would be wonderful, especially if the work is complete -- or very close to complete. [It might also lead to it being considered more seriously by homelab users, SMB (small and medium business) techs, and others.] Thank you for reading, and thank you again for all that you do. Sincerely, JR Sent with [ProtonMail](https://protonmail.com) Secure Email.
