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 0C5FD728B for ; Fri, 30 Mar 2018 17:47:06 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 51D1220F30; Fri, 30 Mar 2018 11:47:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 30 Mar 2018 11:47:06 -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=ZeLJY6aOWJGMq96eVUZjT0p4H6 +e3ZHwVqZLOdNwoE8=; b=gtqty/oVcpCis6wI+KH0RF0JC/oOW/yS+Vg0accP3I sNmJ4WHJpOSLT4aOmzVP+/nO8MiUk0CCnBKStq532jpcULRNtNECiRupEoroxT5F ZKOWoO1v/JvRmjw/4x1WaYqvnIqBjuPRJ04NcQLU63JiVCE3ovLTDlhPcbS2owSe Q= 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=ZeLJY6 aOWJGMq96eVUZjT0p4H6+e3ZHwVqZLOdNwoE8=; b=PP6BKfgEviGl94m6d0SgLs JGPsnfSPHXEUvaF0HPePyMx+XrO/mZU9YmPfS5EDlvKYAGdE2cjxfjGdeUdCWHbu SATc4sMMbuj5MAsUL4Mm5/xlVuE0l7uXE1xRQ+Bky3xAmN5CFIbmw6c1aSEMXHvT D2dB3FdGQKMmj/Kf9w3NYzjJaqdjUYm82XEA1ZquE736c4/Hv7W6P2db550vpbTf HOY/16bH8LCQec+2bGTJ9e2yJik/F552ZJWMVhIkCuL/xII+ycBQhgKB5C4Hnyly kav1YjAeiHqDuJYhGeGaenPIqOgcftF8andBZqM1T3NpgY3Q9Rz2/IXA+fJu4rWQ == 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 584F810255; Fri, 30 Mar 2018 11:47:03 -0400 (EDT) From: Thomas Monjalon To: Andrew Rybchenko Cc: dev@dpdk.org, Ajit Khaparde , Jerin Jacob , Shijith Thotton , Santosh Shukla , 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 , Harish Patil , Rasesh Mody , Shrikrishna Khare , Maxime Coquelin , Allain Legacy , Bruce Richardson , Gaetan Rivet , Olivier Matz Date: Fri, 30 Mar 2018 17:46:48 +0200 Message-ID: <1644846.U24NRPAHE1@xps> In-Reply-To: <93ee347b-3474-30c5-d35e-cd2766dcb34a@solarflare.com> References: <2759953.P7QpFFSjiU@xps> <93ee347b-3474-30c5-d35e-cd2766dcb34a@solarflare.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Fri, 30 Mar 2018 15:47:07 -0000 30/03/2018 17:13, Andrew Rybchenko: > On 03/30/2018 04:47 PM, Thomas Monjalon wrote: > > There is the same kind of confusion in the offload capabilities: > > rte_eth_dev_info.[rt]x_offload_capa > > rte_eth_dev_info.[rt]x_queue_offload_capa > > The queue capabilities must be a subset of port capabilities, > > i.e. every queue capabilities must be reported as port capabilities. > > But the port capabilities should be reported at queue level > > only if it can be applied to a specific queue. > > > > 4/ Do you agree with above statement (to be added in the doc)? > > Yes, may be it would be good to be more precise what "can be applied" mean. > As I understand it is "can be enabled on queue when it is disabled on > port level". Yes, "can be applied to a specific queue" means "can be enabled on queue when it is disabled on port level". Thanks for answering the survey.