From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Anders K. Pedersen | Cohaesio" <akp@cohaesio.com>
Cc: "netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"kaber@trash.net" <kaber@trash.net>
Subject: Re: [PATCH nf] netfilter: nft_dynset: fix element timeout for HZ != 1000
Date: Mon, 17 Oct 2016 17:29:58 +0200 [thread overview]
Message-ID: <20161017152958.GA9045@salvia> (raw)
In-Reply-To: <1476020942.992.20.camel@cohaesio.com>
On Sun, Oct 09, 2016 at 01:49:02PM +0000, Anders K. Pedersen | Cohaesio wrote:
> From: Anders K. Pedersen <akp@cohaesio.com>
>
> With HZ=100 element timeout in dynamic sets (i.e. flow tables) is 10 times
> higher than configured.
>
> Add proper conversion to/from jiffies, when interacting with userspace.
>
> I tested this on Linux 4.8.1, and it applies cleanly to current nf and
> nf-next trees.
Applied, thanks Anders.
prev parent reply other threads:[~2016-10-17 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 13:49 [PATCH nf] netfilter: nft_dynset: fix element timeout for HZ != 1000 Anders K. Pedersen | Cohaesio
2016-10-17 15:29 ` Pablo Neira Ayuso [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=20161017152958.GA9045@salvia \
--to=pablo@netfilter.org \
--cc=akp@cohaesio.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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).