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=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 2F500C433E0 for ; Sun, 10 Jan 2021 07:53:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E77D923A9C for ; Sun, 10 Jan 2021 07:53:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726142AbhAJHx5 (ORCPT ); Sun, 10 Jan 2021 02:53:57 -0500 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:8799 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725785AbhAJHx5 (ORCPT ); Sun, 10 Jan 2021 02:53:57 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Sat, 09 Jan 2021 23:53:16 -0800 Received: from [172.27.13.71] (172.20.145.6) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 10 Jan 2021 07:53:14 +0000 Subject: Re: [net-next 08/15] net/mlx5e: CT: Preparation for offloading +trk+new ct rules From: Roi Dayan To: Marcelo Ricardo Leitner , Saeed Mahameed CC: "David S. Miller" , Jakub Kicinski , , Paul Blakey , Saeed Mahameed , Oz Shlomo References: <20210108053054.660499-1-saeed@kernel.org> <20210108053054.660499-9-saeed@kernel.org> <20210108214812.GB3678@horizon.localdomain> Message-ID: <218258b2-3a86-2d87-dfc6-8b3c1e274b26@nvidia.com> Date: Sun, 10 Jan 2021 09:52:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1610265196; bh=fpbg719HznsR8Q77Ic3JpHFZVD0QA5KN/IHfieFCnnM=; h=Subject:From:To:CC:References:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Language: Content-Transfer-Encoding:X-Originating-IP:X-ClientProxiedBy; b=NsOx5PIfa0CSdqt1wIonfGJZpJD1kQZ08K7Q1jBGPHPfl+FzHDlopj2sGq9sU1Mq/ KHAvNGuRPL7wXjcXrz1zXdLjWXw2stlBUZv9nKZSbuxdJ987iCzwz2d4/8gLvYMhJU Mc52BVoUdupchUuUa7Vt/59kytJ3JaGN++WAza9n5zAAvYWJsSLUvmlOG/6hFgxI0a 3hKeJAI1J2Wpi2bSgUVCBXQTlNsyrWR/U9uZ7MCMjkda2B9vxGAYPE78sjNv8vkpww TRvlr2mYbMZCYAE1SXrrVYdVMoTlAtEeBwhNMS39ImPfc3eVLw4YX3y54NYDDO6T55 9Dbmf0pbDTslA== Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 2021-01-10 9:45 AM, Roi Dayan wrote: >=20 >=20 > On 2021-01-08 11:48 PM, Marcelo Ricardo Leitner wrote: >> Hi, >> >> On Thu, Jan 07, 2021 at 09:30:47PM -0800, Saeed Mahameed wrote: >>> From: Roi Dayan >>> >>> Connection tracking associates the connection state per packet. The >>> first packet of a connection is assigned with the +trk+new state. The >>> connection enters the established state once a packet is seen on the >>> other direction. >>> >>> Currently we offload only the established flows. However, UDP traffic >>> using source port entropy (e.g. vxlan, RoCE) will never enter the >>> established state. Such protocols do not require stateful processing, >>> and therefore could be offloaded. >> >> If it doesn't require stateful processing, please enlight me on why >> conntrack is being used in the first place. What's the use case here? >> >=20 > The use case for example is when we have vxlan traffic but we do > conntrack on the inner packet (rules on the physical port) so > we never get established but on miss we can still offload as normal > vxlan traffic. >=20 my mistake about "inner packet". we do CT on the underlay network, i.e. the outer header. >>> >>> The change in the model is that a miss on the CT table will be forwarde= d >>> to a new +trk+new ct table and a miss there will be forwarded to the=20 >>> slow >>> path table. >> >> AFAICU this new +trk+new ct table is a wildcard match on sport with >> specific dports. Also AFAICU, such entries will not be visible to the >> userspace then. Is this right? >> >> =C2=A0=C2=A0 Marcelo >> >=20 > right.