From: Martin KaFai Lau <martin.lau@linux.dev>
To: David Ahern <dsahern@kernel.org>
Cc: Quentin Deslandes <qde@naccy.de>,
netdev@vger.kernel.org, stephen@networkplumber.org,
Martin KaFai Lau <kafai@fb.com>
Subject: Re: ss: support for BPF sk local storage
Date: Wed, 23 Aug 2023 22:37:41 -0700 [thread overview]
Message-ID: <63e7a517-7918-d05a-c116-75395de5cdee@linux.dev> (raw)
In-Reply-To: <08d0b5ee-fb78-b1ad-2b18-f9fe6fd6c48b@kernel.org>
On 8/23/23 8:33 PM, David Ahern wrote:
> On 8/23/23 6:55 AM, Quentin Deslandes wrote:
>> Hi,
>>
>> Could it be possible to print BPF sk local storage data from ss?
>> Reading the original patch [1], it appears to have been thought
>> out this way, and it seems (to me) that it would fit ss' purpose.
>>
>> Please correct me if my assumptions are wrong.
>>
>> 1. https://lore.kernel.org/netdev/20190426233938.1330361-1-kafai@fb.com/
>>
>> Regards,
>> Quentin Deslandes
>
> Adding Martin, author of the patches.
>
> I have not looked into the details, but if the intent is ss style
> monitoring then please send a patch.
It will be great if ss can print out the bpf sk local storage data of a socket.
It requires some libbpf API (like pretty printing data with btf), so this
storage printing probably should only be supported when a more recent libbpf
with those API is available.
next prev parent reply other threads:[~2023-08-24 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 13:55 ss: support for BPF sk local storage Quentin Deslandes
2023-08-24 3:33 ` David Ahern
2023-08-24 5:37 ` Martin KaFai Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-16 15:39 Quentin Deslandes
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=63e7a517-7918-d05a-c116-75395de5cdee@linux.dev \
--to=martin.lau@linux.dev \
--cc=dsahern@kernel.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=qde@naccy.de \
--cc=stephen@networkplumber.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.