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 9CD2FA052A; Wed, 27 Jan 2021 17:59:05 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4438C140F95; Wed, 27 Jan 2021 17:59:05 +0100 (CET) Received: from smtp-3.sys.kth.se (smtp-3.sys.kth.se [130.237.48.192]) by mails.dpdk.org (Postfix) with ESMTP id D570E140DEC for ; Wed, 27 Jan 2021 17:59:03 +0100 (CET) Received: from smtp-3.sys.kth.se (localhost.localdomain [127.0.0.1]) by smtp-3.sys.kth.se (Postfix) with ESMTP id 7AC5E5B29; Wed, 27 Jan 2021 17:59:03 +0100 (CET) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-3.sys.kth.se ([127.0.0.1]) by smtp-3.sys.kth.se (smtp-3.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WRz8_uQS9_mM; Wed, 27 Jan 2021 17:59:02 +0100 (CET) X-KTH-Auth: barbette [78.129.119.184] DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default; t=1611766742; bh=l/kaP/La0mxU24pJ+itpgvm1Tuyi87S+xnhIEhLgwD0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=oSeknUr6YHFci4MUbPLgP1nxaYO/tgh7zrFHQusfYXyanLi/ABAdi+ZxSdejq/jm7 mBIKzcqN8OffATK1JIqEUGDNKJOtZ2EdH76uFA5WWmu9nhAwW94ujP0fVgguVgMC7e FKYp+VXAZ9JfUX5EY/B+zeKGOsl7aRVOZiPHfYos= X-KTH-mail-from: barbette@kth.se Received: from [192.168.1.75] (host-78-129-119-184.dynamic.voo.be [78.129.119.184]) by smtp-3.sys.kth.se (Postfix) with ESMTPSA id A555836A3; Wed, 27 Jan 2021 17:59:00 +0100 (CET) To: Liron Himi , Stephen Hemminger Cc: dpdk-dev References: <20200506124258.69b138e4@hermes.lan> <20200506131031.6379f80a@hermes.lan> <20200506132342.231ca2ba@hermes.lan> From: Tom Barbette Message-ID: <103f3a2a-83ff-b981-112e-2c90ee17531a@kth.se> Date: Wed, 27 Jan 2021 17:58:59 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000907000008030602090209" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-dev] [EXT] Re: input port in mbuf 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" This is a cryptographically signed message in MIME format. --------------ms000907000008030602090209 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 16/01/2021 =C3=A0 21:01, Liron Himi a =C3=A9crit=C2=A0: > Hi, > > Sorry for rearising this issue again, please check my comments inline > > Liron Himi > > -----Original Message----- > From: Stephen Hemminger > Sent: Wednesday, 6 May 2020 23:24 > To: Liron Himi > Cc: dpdk-dev > Subject: Re: [EXT] Re: [dpdk-dev] input port in mbuf > > On Wed, 6 May 2020 20:17:20 +0000 > Liron Himi wrote: > >> For performance optimizations, we need to know the input DPDK port as = after the buffer was transmitted via our ethdev driver instead of release= it back to the memory-pool we can release it to the originated HW pool o= f the input port. > But you can't be sure where the mbuf came from. > It could be a receive on any vendors driver, or it could be from a priv= ate pool that is used for transmit, or anywhere. > > [L.H.] I'm only referring to PP2->PP2 flow on an Armada platform. For a= ny other flow the transmitted buffer will be returned to its 'mb'. > > Please reconsider the real nature here; the world is not testpmd, l2fwd= , l3fwd etc. > These are the kind of optimizations that break real applications and ca= use more trouble than the benefit for one silly benchmark. > > [L.H.] I don't want to influence application usage, this is why I asked= if there is a location in the mbuf where a driver can put its own info. = Like the private area for the application, but just for the input driver.= > And if there is no such location right now, will it be acceptable to in= troduce such one? Isn't=C2=A0 it the purpose of RTE Mbuf dynamic fields ? You could registe= r a=20 field that only your driver knows about. --------------ms000907000008030602090209--