[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ys9IBYKqlTzkf3jA@google.com>
Date: Wed, 13 Jul 2022 22:32:37 +0000
From: Joe Burton <jevburton@...gle.com>
To: Stanislav Fomichev <sdf@...gle.com>
Cc: Joe Burton <jevburton.kernel@...il.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: Add bpf_map__set_name()
> Asked you internally, but not sure I follow. Can you share more on why
> the following won't fix it for us:
>
> https://lore.kernel.org/bpf/OSZP286MB1725CEA1C95C5CB8E7CCC53FB8869@OSZP286MB1725.JPNP286.PROD.OUTLOOK.COM/
>
> ?
>
> The idea seems to be to get the supplied map name (from the obj)
> instead of using pin name? So why is it not enough?
You're correct, this approach also resolves the issue. No need for this
new API.
Powered by blists - more mailing lists