From: Pengcheng Yang <yangpc@wangsu.com>
To: John Fastabend <john.fastabend@gmail.com>,
Jakub Sitnicki <jakub@cloudflare.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: Pengcheng Yang <yangpc@wangsu.com>
Subject: [PATCH bpf-next 0/3] skmsg: Add the data length in skmsg to SIOCINQ ioctl and rx_queue
Date: Tue, 14 Nov 2023 19:41:57 +0800 [thread overview]
Message-ID: <1699962120-3390-1-git-send-email-yangpc@wangsu.com> (raw)
When using skmsg redirect, the msg is queued in psock->ingress_msg,
and the application calling SIOCINQ ioctl will return a readable
length of 0, and we cannot track the data length of ingress_msg from
the ss tool.
In this patch set, we added the data length in ingress_msg to the
SIOCINQ ioctl and the rx_queue of tcp_diag.
Pengcheng Yang (3):
skmsg: Calculate the data length in ingress_msg
tcp: Add the data length in skmsg to SIOCINQ ioctl
tcp_diag: Add the data length in skmsg to rx_queue
include/linux/skmsg.h | 24 ++++++++++++++++++++++--
net/core/skmsg.c | 4 ++++
net/ipv4/tcp.c | 3 ++-
net/ipv4/tcp_diag.c | 2 ++
4 files changed, 30 insertions(+), 3 deletions(-)
--
2.38.1
next reply other threads:[~2023-11-14 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:41 Pengcheng Yang [this message]
2023-11-14 11:41 ` [PATCH bpf-next 1/3] skmsg: Calculate the data length in ingress_msg Pengcheng Yang
2023-11-14 13:15 ` Eric Dumazet
2023-11-14 11:41 ` [PATCH bpf-next 2/3] tcp: Add the data length in skmsg to SIOCINQ ioctl Pengcheng Yang
2023-11-15 7:20 ` John Fastabend
2023-11-15 11:45 ` Pengcheng Yang
2023-11-17 1:32 ` John Fastabend
2023-11-17 10:59 ` Pengcheng Yang
2023-11-14 11:42 ` [PATCH bpf-next 3/3] tcp_diag: Add the data length in skmsg to rx_queue Pengcheng Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1699962120-3390-1-git-send-email-yangpc@wangsu.com \
--to=yangpc@wangsu.com \
--cc=bpf@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.