From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 830EFC4727D for ; Tue, 6 Oct 2020 15:26:03 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 0FB2D206DD for ; Tue, 6 Oct 2020 15:26:02 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0FB2D206DD Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0BF2C1B96F; Tue, 6 Oct 2020 17:26:01 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EA4991B952 for ; Tue, 6 Oct 2020 17:25:57 +0200 (CEST) IronPort-SDR: MJgGOBy4gj+VvN/3eekQgJAe2ZScGAxIvsiU2wDgwLqUDhTotirw/wTXdmRe9iOWUZwgGhGQdd fmBKVsrRJLaQ== X-IronPort-AV: E=McAfee;i="6000,8403,9765"; a="164672816" X-IronPort-AV: E=Sophos;i="5.77,343,1596524400"; d="scan'208";a="164672816" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2020 08:14:05 -0700 IronPort-SDR: gr2C5ljwM6Q+aFUNEnGZnXLHTtF9CJQl/5FNdhvixw0LjlJGUshmS9D5Z9xCxxKh7sMD1A6+s/ 2iGvjyebEfWg== X-IronPort-AV: E=Sophos;i="5.77,343,1596524400"; d="scan'208";a="460837833" Received: from vmedvedk-mobl.ger.corp.intel.com (HELO [10.213.241.116]) ([10.213.241.116]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2020 08:14:01 -0700 To: David Marchand , Bruce Richardson Cc: dev , Jerin Jacob Kollanukkaran , Ray Kinsella , Thomas Monjalon , "Ananyev, Konstantin" References: From: "Medvedkin, Vladimir" Message-ID: <77c0b481-bced-eaaa-6cbd-e89d9c4b2ee1@intel.com> Date: Tue, 6 Oct 2020 16:13:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v8 0/8] fib: implement AVX512 vector lookup 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi David, On 06/10/2020 15:31, David Marchand wrote: > Hello, > > On Wed, Sep 30, 2020 at 12:35 PM Vladimir Medvedkin > wrote: >> >> This patch series implements vectorized lookup using AVX512 for >> ipv4 dir24_8 and ipv6 trie algorithms. >> Also introduced rte_fib_set_lookup_fn() to change lookup function type. >> Added option to select lookup function type in testfib application. >> >> v8: >> - remove Makefile related changes >> - fix missing doxygen for lookup_type >> - add release notes > > Now that https://git.dpdk.org/dpdk/commit/?id=84fb33fec179ea96f814aed9f658d5a2df20745d > is merged, some bits in this series need rework (patch 4 and 7). > > I see we are adding an API to control which vector implementation of > the lookup is used. > Is this required? > My previous understanding was that the SIMD bitwidth work would supersede this. > I will resend v9 reflecting the latest SIMD bitwidth patches > -- Regards, Vladimir