From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4200EA034F; Wed, 31 Mar 2021 23:55:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D1C9B140EE8; Wed, 31 Mar 2021 23:55:34 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id EA47E140EE6 for ; Wed, 31 Mar 2021 23:55:32 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 661E25C00B0; Wed, 31 Mar 2021 17:55:32 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 31 Mar 2021 17:55:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= vaiBZZD1xloHk9H7kME6+rwuMAM/tCo6Zyx/scr2RVs=; b=0Y5jCD9aFH5OzF6t r3Zg2dFevnisy6zl/4usY+ASsPu4exGt6Pa1Cq2Imsarb8ZSMIxiAVXQA84v7Xze NGekaZiDbQhg14E01Q1Kh7HOGy3kYBgiRA6KG/FFlUvPyDzqBcBz17+2ju4vWZJ+ D17aoeKuwqS8B1bKErZqSY+XoWyRoznqQcY37X1d/qvI8BiE7jIvgiCpE5kNvAX5 9QQkDrs0dbOj+F058NnPMpl8/VeoHZv+PiUaknspjMalw9wF2Gr2YvRlELxgSn/i ThvExc83rxmNTNS4PMGXiQUqZomRx8auZoI1YZERqxHEoQBdMKhZKYaHf2rMIdMX 6WFQUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=vaiBZZD1xloHk9H7kME6+rwuMAM/tCo6Zyx/scr2R Vs=; b=lOdzGTjQ5y8kVWOZhbz1+kP0/awznbOVOFgrMfbftW1EfLomL5x9LuPPC nhTjRr4YuLQAqvw5l0eOBSFkHwuhGBdCSGXdBozYmfULj9LOET2u6P1UXOOywrcR XzKF1g8tYkppymxEgQW2MXsM1muXdBrVGtdi1bPPGwp6l7hNNqNPiiAJ0+3rPZmh GaIGa8eVIZnc0q0z0HSknex3iTkAOckwriAkBxReCUFQNDPgtloDaoyVth6f7BnE ZZHwC8xSm6O+ugZ/T3Bn4MzjZnrLlGQZJrUcSeEA/2MjB7yTIF2C0qCNtyk/CrGi +k51dIp6Z0as2bkpb6U3FI5AZa4EQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeifedgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepkeethedtieevhfeigeejleegudefjeehkeekteeuveeiuedvveeu tdejveehveetnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3CC0224005C; Wed, 31 Mar 2021 17:55:30 -0400 (EDT) From: Thomas Monjalon To: Nick Connolly Cc: Bruce Richardson , Dmitry Kozlyuk , Dmitry Malloy , Jie Zhou , Narcisa Ana Maria Vasile , Olivier Matz , Pallavi Kadam , Tyler Retzlaff , dev@dpdk.org Date: Wed, 31 Mar 2021 23:55:27 +0200 Message-ID: <5131236.apLr1G0U0s@thomas> In-Reply-To: References: <20210320112733.13160-1-dmitry.kozliuk@gmail.com> <8471582.rvcOfDAzBe@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v6 3/5] eal: make OS shims internal X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 31/03/2021 23:45, Nick Connolly: > > > > I don't understand your point. > > I am just proposing to allow some apps to explicitly include the shim > > for their convenience in case they are fully based on DPDK and > > understand the risk of conflict with some other code. >=20 >=20 > Agreed - there=E2=80=99s no harm in doing so. >=20 > My point was simply that for a non-trivial application I suspect it will > have limited value due to the sorts of conflicts that are likely to arise. OK yes. If we expose this header, we should bring it with a disclaimer.