From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id D5BE82C8 for ; Fri, 7 Jul 2017 16:02:23 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8373D20709; Fri, 7 Jul 2017 10:02:23 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 07 Jul 2017 10:02:23 -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:x-sasl-enc; s=mesmtp; bh=a5wp9Ju6C37nXhX T3js5Q7NAn2YYo4DXXeJwz7+W5H0=; b=CrW9h9N0smGq6J2qJNL1C6k+jp6Mm9B tU2Kp+gVKDGBtQ5JhlQM71BC5EtVOrhT0Ppq3RTBdLiEb8GcR7TBcekW0PGxbaVb TXoFMcJwrTydNePItAzvUpNZynGTnqE0ZDRLTgOqucaXUEaSP4/ItU63QqZiiCNl iQ0eciSz2A3E= 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:x-sasl-enc; s= fm1; bh=a5wp9Ju6C37nXhXT3js5Q7NAn2YYo4DXXeJwz7+W5H0=; b=nA3+xce3 IeXE3lbwhJULl9OPJQiBztSDT+uV7VdTUHEmXGI2UgOFiBtkiKGf+c9+57iaPfdP ZRBL+Ju7+92gO6NKxUr2JFJxdRtVSq5FfJ6IovHZCsFTiSGd0G8DM+WqS2RpMt0+ GriiGDJx+IYp9cYzvZrfUhpkrMXmTxsLUZBzQqlnw9EUINOB8//D5F37okLptOXN I2Br2YdPE8+d8UiGWIHB+sYnrZJoUWhA9D6HZ9oFHFKHJ5R+jiGGET3+v53goFAt yef+SBahHSmyxc7W0oxouXpv8au0T8/7NBHuPJW/S1hSq4m7pAhh1PSfQ0bj9Pg+ LAjteIOqUERqIA== X-ME-Sender: X-Sasl-enc: pkD6mWdZQmoDFLjcMMt6gkCKrn+P0MG05D6BytEoyosE 1499436143 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 351CE7E82A; Fri, 7 Jul 2017 10:02:23 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Andrew Rybchenko , John McNamara , dev@dpdk.org, Olivier Matz Date: Fri, 07 Jul 2017 16:02:22 +0200 Message-ID: <1676793.i6e7ich7X3@xps> In-Reply-To: <1f389cf5-ed5d-0768-ab91-76f458a0c219@intel.com> References: <20170622190233.67933-1-ferruh.yigit@intel.com> <8948822.3HyaHf9bfD@xps> <1f389cf5-ed5d-0768-ab91-76f458a0c219@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] doc: document NIC features 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, 07 Jul 2017 14:02:24 -0000 07/07/2017 15:57, Ferruh Yigit: > On 7/7/2017 2:53 PM, Thomas Monjalon wrote: > > 07/07/2017 15:37, Ferruh Yigit: > >> On 7/7/2017 11:55 AM, Andrew Rybchenko wrote: > >>> Also some PMDs have few implementations of the datapath (like vector and > >>> usual). Ideally > >>> we need common way to highlight it. May be it is OK that control path > >>> features are duplicated > >>> in this case, but ideally it should be expressed somehow. > >> > >> I agree different datapath implementations can be documented better, I > >> just don't know how to do ... > >> > >> For some drivers there are multiple vector implementations and the > >> feature set for them is not clear. And as you said control features are > >> duplicated in the table. > >> > >> Perhaps control and datapath features can be separated. > >> > >> Or as Thomas suggested sometime ago, vector and scalar version can be > >> merged into one in the table and feature can be marked as supported if > >> both scalar and vector has support for it. But this is not solving > >> multiple vector implementation problem. > > > > Yes it is the way to go. > > The features should not be different from a datapath implementation to > > another one. So they must be merged in only one column. > > If a feature is not supported in every datapaths of a driver, it should > > be marked as partially supported... and the developers must implement it. > > But for example for i40e, there are altivec, neon and sse vector > implementations, how should we document this? They are all only one i40 driver. It should offer the same features regardless of the platform it runs on. So it should be only one column in the table.