From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f194.google.com (mail-wr0-f194.google.com [209.85.128.194]) by dpdk.org (Postfix) with ESMTP id 849EE912D for ; Thu, 17 Aug 2017 17:25:38 +0200 (CEST) Received: by mail-wr0-f194.google.com with SMTP id n88so9009425wrb.0 for ; Thu, 17 Aug 2017 08:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-transfer-encoding:mime-version; bh=rRg7L/m/86ZJ8Q2KDrVV/V1e7QBhRyIEVvxXjk0+mi0=; b=XMtUKOWwv5x4MI6snubad+kU5XLQFKejlE+AxUCs55gvTRQSNNLS4XlrLLvlZw/1Dp Z5X2cO1XMKlLXfJRElrciLt9y9r28d6qVi5niKbVyOZB6q6RyyWBk3M/1sTbnfHxHVqS nLmpwteuVj2UyR35eQDqLAADd9yoXLCPp9WTMOJTCm7zfPZ1CV0K7TUMO88U2j1jv6Xc E3cKAds8gaEqPl5Pkh5Agh+8/HUaLiyGv0k0590MHiPiE4PMLlTsTS91bzExr512FuOf 3qNpQCfsrwGeQauqjT3jg/eE3Xneg9JE+1L3mZdXhYJ0xVUaLxNgBHqRHwTLvlvUzjuQ rLpQ== 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=rRg7L/m/86ZJ8Q2KDrVV/V1e7QBhRyIEVvxXjk0+mi0=; b=WVyImeQV2VkjzZh6BOb+8mRyw8vK8JfDVmjIVm3q799kx9ieHBUkKs5ZybRVuxFb2D P3j2az47GhC5SFqfFz1TfodgSE8GnRNEo8wUSLarTdD8C7F4t/EOQEzF164LG+FWkwOL 2kuUe0FYGGAD7ZwwTamnRhE01adFfGavYo+kRldW0qzApSQG8fZZsYqZwJ5QeQfqS+7r AiMYn8ixpHFTXP+iJNcbPQN51JIGJa+bA108zyuEXS7yvLEpydaCisgS4ex1Y1caaIf/ y/2vRxKo1Zelu5BPn7IFos5XJw0e54prd5t1EPXSaF9UwUWVkKCwx0FHXOp2WU+KRiz8 Ku2A== X-Gm-Message-State: AHYfb5h8+IBMbKJw7xuWGH7t9sEjLOTNJS4V6AqiIwBperht9l+gv293 /T6mxeWCx7z62Q== X-Received: by 10.223.162.217 with SMTP id t25mr3970741wra.68.1502983538245; Thu, 17 Aug 2017 08:25:38 -0700 (PDT) Received: from localhost ([2a00:23c5:bef3:400:4a51:b7ff:fe0b:4749]) by smtp.gmail.com with ESMTPSA id k10sm113594wmb.42.2017.08.17.08.25.37 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 Aug 2017 08:25:37 -0700 (PDT) Message-ID: <1502983536.31476.4.camel@gmail.com> From: Luca Boccassi To: Marco Varlese , Bruce Richardson , dev@dpdk.org Cc: thomas@monjalon.net Date: Thu, 17 Aug 2017 16:25:36 +0100 In-Reply-To: <1502979024.15962.10.camel@suse.com> References: <20170814095208.166496-1-bruce.richardson@intel.com> <1502979024.15962.10.camel@suse.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Subject: Re: [dpdk-dev] [RFCv2 00/40] Building DPDK with meson and ninja 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: , X-List-Received-Date: Thu, 17 Aug 2017 15:25:38 -0000 On Thu, 2017-08-17 at 16:10 +0200, Marco Varlese wrote: > Hi Bruce, >=20 > On Mon, 2017-08-14 at 10:51 +0100, Bruce Richardson wrote: > > Following on from previous RFC [http://dpdk.org/dev/patchwork/patch > > /25104/] > > here is a second draft implementation for building DPDK with meson > > and > > ninja. While still not building all of DPDK, and needing patch > > cleanup so > > that patches don't overwrite previous work, it is more complete in > > many > > ways than the previous version and includes: > >=20 > > * dynamic build configuration e.g. building pcap driver only if > > pcap is > > =C2=A0 found, only build af_packet if the target is linux, and only > > building QAT > > =C2=A0 and openssl crypto drivers if libcrypto is found > > * support for pmdinfo inside the PMDs(for shared builds) and > > binaries (for > > =C2=A0 static builds) > > * generalized/standardized way of building libs and drivers, though > > the > > =C2=A0 drivers code still needs generalization at the driver, rather > > than > > =C2=A0 driver-class level. > > * support for having a pkgconfig file for DPDK on install, and > > helloworld > > =C2=A0 and l2fwd can be built using the pkgconfig info (via make, not > > ninja) > > * support for library versions > > * an implementation for FreeBSD as well as Linux > > * all libraries are included in the build, as well as a number of > > NIC, > > =C2=A0 crypto, and mempool drivers > > * the igb_uio kernel module is build via the kernel Kbuild system > > as part > > =C2=A0 of a meson/ninja DPDK build >=20 > This is really great to see. I do have one suggestion. > Would it be possible to version the libraries built by the build- > system > following the same version of the DPDK release? >=20 > For instance, in DPDK 17.08 we currently have: > # objdump -p librte_pmd_ixgbe.so.1 |grep SONAME > =C2=A0 SONAME=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0librte_pmd_ixgbe.so.1 >=20 > Would it make sense to instead have librte_pmd_ixgbe.so.17.08 >=20 > I think it would help to facilitate the installation of multiple DPDK > library > versions on the same system.=C2=A0 >=20 > For example, we could have the following scenario: >=20 > 1) OpenVSwithc linked with version 17.02 of DPDK > 2) VPP linked with version 17.08 of DPDK > 3) DPDK 18.xx installed in the system for any cutting-edge > application > prototyping. >=20 > Is this something which could be incorporated as part of this work? Christian sent a patch a while ago, which was merged, to enable this in the current build system, it's the CONFIG_RTE_MAJOR_ABI option, we use it in Debian and Ubuntu for the reasons you mentioned. And if it's not been translated yet, I agree it's an important one. --=20 Kind regards, Luca Boccassi