From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 5F326A05D3 for ; Sun, 24 Mar 2019 13:07:22 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 440E41B869; Sun, 24 Mar 2019 13:07:21 +0100 (CET) Received: from mail-wm1-f67.google.com (mail-wm1-f67.google.com [209.85.128.67]) by dpdk.org (Postfix) with ESMTP id D698E1B857 for ; Sun, 24 Mar 2019 13:07:19 +0100 (CET) Received: by mail-wm1-f67.google.com with SMTP id y197so6249394wmd.0 for ; Sun, 24 Mar 2019 05:07:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=mz3l5SZHNg/3I6caBiIckTH0oHj9zLPxlxS8grx2Fww=; b=UQoNpBxWvwfVWRlTB77L/3scNY1lO6+laguhzPVYzMj+kLwLQ/NWxY61DFgtKG6hvD 8KuiZ+1xKFLVJu/ANAXOmeagWR311DAvFdmIB1/zP6FwOS6E/RH4E0HJZIz/NnjDVoVQ AwoajTe/MdbnN6S8IV2bY6x4TXIYhb5IePbj2Lbcq8199ieG1PcaNcO0/nGqCoVWX4EJ bx+hdVMWfjk0GFt0NAShfJDAipbdoL+aGktli4z9OCk5hezM424tx5oaaiI1GDPzyzli 1qisciUTNr57TT8SoyqsojPxCICQYzAUQhA3NzCXVMb4YpoLQYJbysAyCld5+PI72uj/ 2law== X-Gm-Message-State: APjAAAUKKbLt8MoXVwoRfGVGyU08kVOqoUP3lRu18/C29uuacSzB3gRR wlFh5WAzuvSlkWoHiRspJ6U= X-Google-Smtp-Source: APXvYqzY9CHZ2M/ft4gkdMg07i8VF3BZzu4yZBhmuI1yQyklHwycf9vcV2LUFCk4b6wk+FlSDlv0Ag== X-Received: by 2002:a1c:e910:: with SMTP id q16mr9041617wmc.30.1553429239520; Sun, 24 Mar 2019 05:07:19 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:5044:c29d:d518:fd30]) by smtp.gmail.com with ESMTPSA id j66sm23774968wrj.51.2019.03.24.05.07.17 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 24 Mar 2019 05:07:18 -0700 (PDT) Message-ID: <1553429237.20876.3.camel@debian.org> From: Luca Boccassi To: Ye Xiaolong Cc: dev@dpdk.org, Qi Zhang Date: Sun, 24 Mar 2019 12:07:17 +0000 In-Reply-To: <20190317033425.GA103486@intel.com> References: <20190301080947.91086-1-xiaolong.ye@intel.com> <20190301080947.91086-2-xiaolong.ye@intel.com> <20190302081407.GD100586@intel.com> <20190317033425.GA103486@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v1 1/6] net/af_xdp: introduce AF_XDP PMD driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190324120717.nt5_B4ebKogHdY8P5dlupBxQoSMPlt0R1yeMhpag0Hg@z> On Sun, 2019-03-17 at 11:34 +0800, Ye Xiaolong wrote: > On 03/02, Ye Xiaolong wrote: > > > > =C2=A0_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_AF_PACKET)=C2=A0=C2=A0+=3D > > > > -lrte_pmd_af_packet > > > > +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_AF_XDP)=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0+=3D > > > > -lrte_pmd_af_xdp > > > > -lelf -lbpf > > >=20 > > > Are symbols from libelf being used by the PMD? > >=20 > > Hmm, it is a leftover of RFC, libelf is no longer needed in this > > version, will > > remove it in next version. > >=20 >=20 > Correction, libelf is needed for libbpf, so we still need to keep > it.=C2=A0 If libbpf needs libelf for its internal usage, it should be linked against it itself. Unless symbols from libelf are used in static functions defined in libbpf's public headers. Is this the case? --=20 Kind regards, Luca Boccassi