From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: SIMD Rx/Tx paths Date: Mon, 15 May 2017 14:35:55 +0200 Message-ID: <1857248.OtrprS2xZT@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Yuanhan Liu , Maxime Coquelin , Jing Chen , Helin Zhang , Jingjing Wu , Wenzhuo Lu , Konstantin Ananyev , Bruce Richardson To: ferruh.yigit@intel.com Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 141CB3B5 for ; Mon, 15 May 2017 14:35:57 +0200 (CEST) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, I would like to open a discussion about SIMD code in drivers. I think we should not have different behaviours or features capabilities, in the different code paths of a same driver. I suggest to consider such differences as exceptions. So we should merge features files (i.e. matrix columns), and remove these files: % ls doc/guides/nics/features/*_vec.ini doc/guides/nics/features/fm10k_vec.ini doc/guides/nics/features/fm10k_vf_vec.ini doc/guides/nics/features/i40e_vec.ini doc/guides/nics/features/i40e_vf_vec.ini doc/guides/nics/features/ixgbe_vec.ini doc/guides/nics/features/ixgbe_vf_vec.ini doc/guides/nics/features/virtio_vec.ini If a feature is not supported in all code paths of a driver, it must be marked as partially (P) supported. Then the mid-term goal will be to try removing these inconsistencies. Opinions/comments?