From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E58E8C433EF for ; Wed, 13 Jul 2022 22:32:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237091AbiGMWcp (ORCPT ); Wed, 13 Jul 2022 18:32:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229638AbiGMWco (ORCPT ); Wed, 13 Jul 2022 18:32:44 -0400 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CF3924D4FC for ; Wed, 13 Jul 2022 15:32:43 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id v4-20020a17090abb8400b001ef966652a3so6062241pjr.4 for ; Wed, 13 Jul 2022 15:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=IC9WGNm/k/HKk/gJGNaIvhPEN6uro4h2Di4XSx0/wSo=; b=OkSo1h56KPB5dkuCz8RIEJrgSYw4gI07VeoymulEGnmJB6DcrjGkznYuVr404v6pt+ 9yHloAN4Q07BaVh71sQpHnPVZNumFT7r5SE3nqXAUTn0roPwGbrTLVS9ahctp1L8a+rq 0eps4wB9X7CAyqmAtmPUpchkdoEpFGHoNamrQl92nN/VEKkskeKEDPMM0ofVu6bqmp9D 2WLtOCI3Q6SNyOM4dA8/xuE/qSWNruUPJy1Pd8wbmIy4yw30BUz+lSMl86wtaz1GIOv1 /EpmiXBWNYnqo1hSvyQOIr7nXZT4xJ3AtRU6/rs7O09UaEfzBGIULZcvMZkk9pmQufia S4UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=IC9WGNm/k/HKk/gJGNaIvhPEN6uro4h2Di4XSx0/wSo=; b=FKoETP7hFnOIERcNMn4CKkEVTDElb2O7PyWZ9aJx6oXKAl72qwXisX5eBsL6iMjsDa Eq7WvnvDx/BkUBfz57izTCKDmVqNW196HSOunPJFbqnVlM4lQ4pUfSYGoTOHcl5T7xPV Xi6C1aLzGrNf7i5Ek7kNUA+t17ddUspq3VKM5dzlhK5WkeFZTZ8p4hDqTJ9tZiAcnPWD LAXDrdFr9+OSVkjPn8is79/m1/e3KCzBjnExRAS7qEddx6deL1T85dpH+iNWkiDWHa4J /DAGsGdEJ3B0RHeKKKJe8CK8dCpxq2HB3vR8Vi0phTAff6FzNf5gPjUa5D27XdQOWaaD AGXA== X-Gm-Message-State: AJIora9058XegO0w8GgCFvknaTtn/Nk8/+ReM7taVnOFhO6us/GvYESO ykLsNyIufRFjIBY+MKyA1hRbjjrFHQ2or7tD X-Google-Smtp-Source: AGRyM1uM2JXWmZ+X73tly9ctALwOfHOQQW2AF5qxNd9TwdS/gxM4q6HbjbNoMiJYW+NrmS56kvEVZg== X-Received: by 2002:a17:902:c409:b0:16c:10a2:afa8 with SMTP id k9-20020a170902c40900b0016c10a2afa8mr5250538plk.105.1657751563227; Wed, 13 Jul 2022 15:32:43 -0700 (PDT) Received: from google.com (223.103.125.34.bc.googleusercontent.com. [34.125.103.223]) by smtp.gmail.com with ESMTPSA id i15-20020aa796ef000000b00528c6c7bf37sm43808pfq.129.2022.07.13.15.32.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Jul 2022 15:32:42 -0700 (PDT) Date: Wed, 13 Jul 2022 22:32:37 +0000 From: Joe Burton To: Stanislav Fomichev Cc: Joe Burton , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Hao Luo , Jiri Olsa , bpf@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH bpf-next] libbpf: Add bpf_map__set_name() Message-ID: References: <20220713214246.2545204-1-jevburton.kernel@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org > 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.