From: Yonghong Song <yhs@meta.com>
To: Xueming Feng <kuro@kuroa.me>
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
quentin@isovalent.com, sdf@google.com, song@kernel.org,
yhs@fb.com
Subject: Re: [PATCH bpf-next v2] bpftool: Dump map id instead of value for map_of_maps types
Date: Mon, 24 Apr 2023 22:58:10 -0700 [thread overview]
Message-ID: <561b0f03-4a3a-89d3-5793-a0d69535ca0f@meta.com> (raw)
In-Reply-To: <20230425041050.59727-1-kuro@kuroa.me>
On 4/24/23 9:10 PM, Xueming Feng wrote:
>> On 4/24/23 2:09 AM, Xueming Feng wrote:
>>> When using `bpftool map dump` in plain format, it is usually
>>> more convenient to show the inner map id instead of raw value.
>>> Changing this behavior would help with quick debugging with
>>> `bpftool`, without disrupting scripted behavior. Since user
>>> could dump the inner map with id, and need to convert value.
>>>
>>> Signed-off-by: Xueming Feng <kuro@kuroa.me>
>>> ---
>>> Changes in v2:
>>> - Fix commit message grammar.
>>> - Change `print_uint` to only print to stdout, make `arg` const, and rename
>>> `n` to `arg_size`.
>>> - Make `print_uint` able to take any size of argument up to `unsigned long`,
>>> and print it as unsigned decimal.
>>>
>>> Thanks for the review and suggestions! I have changed my patch accordingly.
>>> There is a possibility that `arg_size` is larger than `unsigned long`,
>>> but previous review suggested that it should be up to the caller function to
>>> set `arg_size` correctly. So I didn't add check for that, should I?
>>>
>>> tools/bpf/bpftool/main.c | 15 +++++++++++++++
>>> tools/bpf/bpftool/main.h | 1 +
>>> tools/bpf/bpftool/map.c | 9 +++++++--
>>> 3 files changed, 23 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tools/bpf/bpftool/main.c b/tools/bpf/bpftool/main.c
>>> index 08d0ac543c67..810c0dc10ecb 100644
>>> --- a/tools/bpf/bpftool/main.c
>>> +++ b/tools/bpf/bpftool/main.c
>>> @@ -251,6 +251,21 @@ int detect_common_prefix(const char *arg, ...)
>>> return 0;
>>> }
>>>
>>> +void print_uint(const void *arg, unsigned int arg_size)
>>> +{
>>> + const unsigned char *data = arg;
>>> + unsigned long val = 0ul;
>>> +
>>> + #if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
>>> + memcpy(&val, data, arg_size);
>>> + #else
>>> + memcpy((unsigned char *)&val + sizeof(val) - arg_size,
>>> + data, arg_size);
>>> + #endif
>>> +
>>> + fprintf(stdout, "%lu", val);
>>> +}
>>> +
>>> void fprint_hex(FILE *f, void *arg, unsigned int n, const char *sep)
>>> {
>>> unsigned char *data = arg;
>>> diff --git a/tools/bpf/bpftool/main.h b/tools/bpf/bpftool/main.h
>>> index 0ef373cef4c7..0de671423431 100644
>>> --- a/tools/bpf/bpftool/main.h
>>> +++ b/tools/bpf/bpftool/main.h
>>> @@ -90,6 +90,7 @@ void __printf(1, 2) p_info(const char *fmt, ...);
>>>
>>> bool is_prefix(const char *pfx, const char *str);
>>> int detect_common_prefix(const char *arg, ...);
>>> +void print_uint(const void *arg, unsigned int arg_size);
>>> void fprint_hex(FILE *f, void *arg, unsigned int n, const char *sep);
>>> void usage(void) __noreturn;
>>>
>>> diff --git a/tools/bpf/bpftool/map.c b/tools/bpf/bpftool/map.c
>>> index aaeb8939e137..f5be4c0564cf 100644
>>> --- a/tools/bpf/bpftool/map.c
>>> +++ b/tools/bpf/bpftool/map.c
>>> @@ -259,8 +259,13 @@ static void print_entry_plain(struct bpf_map_info *info, unsigned char *key,
>>> }
>>>
>>> if (info->value_size) {
>>> - printf("value:%c", break_names ? '\n' : ' ');
>>> - fprint_hex(stdout, value, info->value_size, " ");
>>> + if (map_is_map_of_maps(info->type)) {
>>> + printf("id:%c", break_names ? '\n' : ' ');
>> 1> + print_uint(value, info->value_size);
>
> On Mon, 24 Apr 2023 18:07:27 -0700, Yonghong Song wrote:
>> For all map_in_map types, the inner map value size is 32bit int which
>> represents a fd (for map creation) and a id (for map info), e.g., in
>> show_prog_maps() in prog.c. So maybe we can simplify the code as below:
>> printf("id: %u", *(unsigned int *)value);
>
> That is true, maybe the "id" could also be changed to "map_id" to follow the
> convention. Do you think that `print_uint` could be useful in the future?
> If that is the case, should I keep using it here as an example usage, and to
> avoid dead code? Or should I just remove it?
Maybe, "inner_map_id" is a better choice. For array of maps, some array
element value could be 0, implying "inner_map_id 0", but I think it is
okay, people should know a real inner_map_id (or any map_id) should
never be 0.
Function "print_uint" is not needed any more. Please remove it.
Please add the command line to dump map values triggering the above
change, also the actual dumps with and without this patch.
>
>>> + } else {
>>> + printf("value:%c", break_names ? '\n' : ' ');
>>> + fprint_hex(stdout, value, info->value_size, " ");
>>> + }
>>> }
>>>
>>> printf("\n");
next prev parent reply other threads:[~2023-04-25 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:09 Xueming Feng
2023-04-24 16:44 ` Kui-Feng Lee
2023-04-25 3:58 ` Xueming Feng
2023-04-25 5:19 ` Kui-Feng Lee
2023-04-25 6:09 ` Xueming Feng
2023-04-25 1:07 ` Yonghong Song
2023-04-25 4:10 ` Xueming Feng
2023-04-25 5:58 ` Yonghong Song [this message]
2023-04-25 6:37 ` Xueming Feng
2023-04-25 8:57 ` Quentin Monnet
2023-04-25 9:52 ` Xueming Feng
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=561b0f03-4a3a-89d3-5793-a0d69535ca0f@meta.com \
--to=yhs@meta.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuro@kuroa.me \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®