From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 3/5] net/szedata2: refactor ibuf and obuf address definition Date: Mon, 29 May 2017 13:41:30 +0100 Message-ID: References: <1495821956-5050-1-git-send-email-vido@cesnet.cz> <1495821956-5050-3-git-send-email-vido@cesnet.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit To: Matej Vido , dev@dpdk.org Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2418A7CBF for ; Mon, 29 May 2017 14:41:32 +0200 (CEST) In-Reply-To: <1495821956-5050-3-git-send-email-vido@cesnet.cz> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 5/26/2017 7:05 PM, Matej Vido wrote: > This is to prepare for firmwares with multiple ibufs and obufs. > Offsets of ibufs and obufs are defined in array. I was thinking ibufs and obufs as queues, but since link functions updated per ibufs it looks like ports, can you please provide some information what is ibufs and obufs? What is the benefit of having multiple ibufs and obufs? > Functions which operate on ibufs and obufs iterate over this array. > > Signed-off-by: Matej Vido <...>