From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH V3 1/3] table: improve learner table timers
Date: Wed, 01 Jun 2022 15:57:26 +0200 [thread overview]
Message-ID: <2138409.1BCLMh4Saa@thomas> (raw)
In-Reply-To: <20220520221255.1731-1-cristian.dumitrescu@intel.com>
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 <cristian.dumitrescu@intel.com>
Series applied, thanks.
prev parent reply other threads:[~2022-06-01 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 15:59 [PATCH " Cristian Dumitrescu
2022-04-21 15:59 ` [PATCH 2/3] pipeline: " Cristian Dumitrescu
2022-04-21 15:59 ` [PATCH 3/3] examples/pipeline: " Cristian Dumitrescu
2022-04-22 13:03 ` [PATCH V2 1/3] table: " Cristian Dumitrescu
2022-04-22 13:03 ` [PATCH V2 2/3] pipeline: " Cristian Dumitrescu
2022-04-22 13:03 ` [PATCH V2 3/3] examples/pipeline: " Cristian Dumitrescu
2022-05-20 22:12 ` [PATCH V3 1/3] table: " Cristian Dumitrescu
2022-05-20 22:12 ` [PATCH V3 2/3] pipeline: " Cristian Dumitrescu
2022-05-20 22:12 ` [PATCH V3 3/3] examples/pipeline: " Cristian Dumitrescu
2022-06-01 13:57 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2138409.1BCLMh4Saa@thomas \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).