diff options
| author | Jakub Kicinski <[email protected]> | 2023-06-06 03:51:57 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2023-06-06 03:51:58 +0000 |
| commit | ddb8701dcb67aff0155d507c63cb1e201daf3ad6 (patch) | |
| tree | 6a148c7950b18e5f9a7234610561b1d6bfde0d6a /lib/net_utils.c | |
| parent | Merge tag 'mlx5-updates-2023-05-31' of git://git.kernel.org/pub/scm/linux/ker... (diff) | |
| parent | kcm: Convert kcm_sendpage() to use MSG_SPLICE_PAGES (diff) | |
| download | kernel-ddb8701dcb67aff0155d507c63cb1e201daf3ad6.tar.gz kernel-ddb8701dcb67aff0155d507c63cb1e201daf3ad6.zip | |
Merge branch 'splice-net-handle-msg_splice_pages-in-af_kcm'
David Howells says:
====================
splice, net: Handle MSG_SPLICE_PAGES in AF_KCM
Here are patches to make AF_KCM handle the MSG_SPLICE_PAGES internal
sendmsg flag. MSG_SPLICE_PAGES is an internal hint that tells the protocol
that it should splice the pages supplied if it can. Its sendpage
implementation is then turned into a wrapper around that.
Does anyone actually use AF_KCM? Upstream it has some issues. It doesn't
seem able to handle a "message" longer than 113920 bytes without jamming
and doesn't handle the client termination once it is jammed.
Link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=51c78a4d532efe9543a4df019ff405f05c6157f6 # part 1
Link: https://lore.kernel.org/r/[email protected]/ # v1
====================
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'lib/net_utils.c')
0 files changed, 0 insertions, 0 deletions