Hi Günther, > Date: 2026-10-16 19:31:20+0200 > From: Günther Noack > > For non-listening sockets, sk_diag_show_rqlen() in linux.git > net/unix/diag.c sets udiag_wqueue to unix_outq_len(), which returns > sk_wmem_alloc_get(): the send-buffer memory currently charged to queued > outgoing data. The value grows as data is queued; it is not the amount > of space remaining. > > Fixes: 4f6a0a4a (2016-12-07; "sock_diag.7: New page documenting NETLINK_SOCK_DIAG interface") > Assisted-by: LLM > Signed-off-by: Günther Noack > --- > > Notes: > Verified in kernel code; the udiag_wqueue field does indeed have these > different semantics -- it's the data already sent, which is still > stuck in the output queue, not the maximum size of the output queue. Not trivial enough for me. Please CC the original authors and also make it more obviously correct. It might help showing snippets of the relevant kernel code. Have a lovely day! Alex > > man/man7/sock_diag.7 | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/man/man7/sock_diag.7 b/man/man7/sock_diag.7 > index 35a6d5a80ffc..8f8b28b4404d 100644 > --- a/man/man7/sock_diag.7 > +++ b/man/man7/sock_diag.7 > @@ -248,7 +248,9 @@ the backlog size which equals to the value passed as the second argument to > .BR listen (2). > .IP > For established sockets: > -the amount of memory available for sending. > +the amount of memory currently allocated for data > +that was sent on this socket > +but has not yet been received by the peer. > .RE > .TP > .B UDIAG_SHOW_MEMINFO > -- > 2.56.0 > > --