From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3A7B9A0548; Wed, 1 Jun 2022 15:57:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D95B640689; Wed, 1 Jun 2022 15:57:34 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id D82884003F for ; Wed, 1 Jun 2022 15:57:32 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 8313C5C029C; Wed, 1 Jun 2022 09:57:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 01 Jun 2022 09:57:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1654091851; x= 1654178251; bh=UrQXjEpSaAb0mDElHa4mT1PaQGKsOw5s9t8QsOX9dl0=; b=Y k//mKHOjxECJ1bt1l4CY7PJOckTdVMD4GhbNp9pb2o6Q4whQN1Lzw+/fdHLjidpU nx3zMp421coABuummYtXSkGHrqAGNkRmTL8W3eqsvHoXAAu6MVEh/dT2KGJZe6Ly 4O2sX+Ibf6wMUd1Wp2lPPCJFu0B+CP+LtxF5b/9B9b1hXM8qQxxbJmRYHtncHtgw 9wSrBiM2sEqLNTmLsj/6t0TYatEu/NiPyqrrg0Em4WdYMkSJWNPsTaOSPNjRR7hi tWTFWbWjFocZv4FUEP6jPXEcuBfTkYvCj9thtN7snb68/eqsgwkVUAat+H/psJlU zBPJCWHPlDduiOdAQnm/w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1654091851; x= 1654178251; bh=UrQXjEpSaAb0mDElHa4mT1PaQGKsOw5s9t8QsOX9dl0=; b=p lKgFd9ct+BRjotvF5OEoTZuVqDv0SmdBoA++TubMEkk0gLitYI1LeVF+jKFQ4NAZ 8nJKj6ccIJALJFThXHwwhVfRQr65ufz+8ixKpFWUKy68AsxSWn9wFYmuDXzm96I8 DcGabtEYh2N76mYI+ehqkdCg6/93Mnqd3GtiWHMmmXgyGGO3b/R6/49mTraOD1Pq gIKyjBYI9FcvCWY17NDkwAq+ou8etuhRvFus9P7I5jAPbZhK3vG+pURxGbJ4mj6P pJzmkdObJ9v4tVP6Oo+I/j2Yn47YAiIxLmWb9TVEHN725tKeIIQdcPS4otbbOq0f oxKBKxwFh62tTPhdkvImA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrledtgdeilecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Jun 2022 09:57:30 -0400 (EDT) From: Thomas Monjalon To: Cristian Dumitrescu Cc: dev@dpdk.org Subject: Re: [PATCH V3 1/3] table: improve learner table timers Date: Wed, 01 Jun 2022 15:57:26 +0200 Message-ID: <2138409.1BCLMh4Saa@thomas> In-Reply-To: <20220520221255.1731-1-cristian.dumitrescu@intel.com> References: <20220422130343.44060-1-cristian.dumitrescu@intel.com> <20220520221255.1731-1-cristian.dumitrescu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 21/05/2022 00:12, Cristian Dumitrescu: > Previously, on lookup hit, the hit key had its timer automatically > rearmed with the same timeout in order to prevent its expiration. Now, > a broader set of actions is available on lookup hit, which has to be > managed explicitly: the key can have its timer rearmed with the same > or with a different timeout, or the key timer can be left unmodified. > The latter option allows the key to expire naturally when the timer > eventually runs out, unless the key is hit again and its timer rearmed > at that point. Needed by the TCP connection tracking state machine. > > Signed-off-by: Cristian Dumitrescu Series applied, thanks.