From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 449821B3C6 for ; Mon, 2 Apr 2018 22:10:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C1CF020C68; Mon, 2 Apr 2018 16:10:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 02 Apr 2018 16:10:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ay9r4kfxhmi7q+21ry/lOHT7E5 TTrB12IBM6Ynz5qNw=; b=hdgCMS9sKV1zbsfbZzatCLcq8wg7j3H8ADN/DUtg93 dEZzucKh0zQDamw8yyQ9NSD7+bt17EdhwWkCXHoV0c1T92fu5vMioGd5MW3UV9Oh ntww9uCq2qBlgcaW73AybKZgkeeIWCEjSU22/0xX15CoGhoBV+QF0+wbIvO3INES 0= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ay9r4k fxhmi7q+21ry/lOHT7E5TTrB12IBM6Ynz5qNw=; b=JDiSsLvZJhz5d0I6fyvS0D VPY0VTgPMcSUhrU5gxzfsz3a4uq5MfCXzqyNCdm2zsoE0HJhvs5qvuRtudE1oI9p 56+xv9cOJmXBnVutB/ywD1ppf3BFAAa7CGPUtURxAOL1DziPURwkI1ypX+jt9kS1 40VGEsccmXH7YNcEUSHxvVjaEyX27c7xoK3NAMP/0jXlKFypY4XFH9ZnEGNXJKDl JaHkJF8X7//pKYizyOlnFLpZiPfs0JZKE0fXWeZWJEkGp1BPWN8JfOL96xw9+Uwq rQ7f6dkcc8xSJ5LhwuvUi0MjM7ZJwNWppNJg8sDFaaW3eXNSdB09FUK8up0Ee2PA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9CBE2E444F; Mon, 2 Apr 2018 16:10:30 -0400 (EDT) From: Thomas Monjalon To: "Patil, Harish" Cc: "dev@dpdk.org" , Ajit Khaparde , "Jacob, Jerin" , "Thotton, Shijith" , "Shukla, Santosh" , Rahul Lakkireddy , John Daley , Wenzhuo Lu , Konstantin Ananyev , Beilei Xing , Qi Zhang , Jingjing Wu , Adrien Mazarguil , Nelio Laranjeiro , Yongseok Koh , Shahaf Shuler , Tomasz Duszynski , Jianbo Liu , Alejandro Lucero , Hemant Agrawal , Shreyansh Jain , "Mody, Rasesh" , Andrew Rybchenko , Shrikrishna Khare , Maxime Coquelin , Allain Legacy , Bruce Richardson , Gaetan Rivet , Olivier Matz Date: Mon, 02 Apr 2018 22:10:14 +0200 Message-ID: <3635124.eX5m4pFW80@xps> In-Reply-To: References: <2759953.P7QpFFSjiU@xps> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] Survey for final decision about per-port offload API 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: Mon, 02 Apr 2018 20:10:34 -0000 02/04/2018 19:39, Patil, Harish: > >It was also proposed to relax the API and allow "forgetting" port > >offloads in queue offloads: > > http://dpdk.org/ml/archives/dev/2018-March/092978.html > > > >It would mean the offloads applied to a queue result of OR operation: > > rte_eth_conf.[rt]xmode.offloads | rte_eth_[rt]xconf.offloads > > > >1/ Do you agree with above API change? >=20 > Yes. But pls confirm that this would still work properly if RX supports > port-only based offloads and doesn=E2=80=99t support queue based offloads= at all, > as advertised in dev_infos_get(). >=20 > dev_info->rx_queue_offload_capa =3D 0 and > dev_info->rx_offload_capa =3D (DEV_RX_OFFLOAD_IPV4_CKSUM | ...); Yes, of course, no queue offload at all is possible.