From: Florian Westphal <fw@strlen.de>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf v2] netfilter: conntrack: refine gc worker heuristics
Date: Fri, 4 Nov 2016 10:07:26 +0100 [thread overview]
Message-ID: <20161104090726.GA16482@breakpoint.cc> (raw)
In-Reply-To: <8aad7dbf-da86-9afc-805c-879833aa2883@6wind.com>
Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
> > However, I will not send a new iteration of this change since I don't
> > know how to test this. Its easy to make the delay low, but it will come
> > at additonal cpu cost. I have no idea where to make the tradeoff.
> For me, the priority is to deliver events with a reasonnable delay (and I think
> Pablo also asks for this in a previous email). I understand that the cpu cost
> need to be taken into account, but it's a tradeoff of the new design I think.
I sent one last iteration. Other than exporting max time as a sysctl
like in your proposal I am out of ideas.
prev parent reply other threads:[~2016-11-04 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 23:04 [PATCH nf v2] netfilter: conntrack: refine gc worker heuristics Florian Westphal
2016-11-03 16:03 ` Nicolas Dichtel
2016-11-03 16:31 ` Florian Westphal
2016-11-03 16:57 ` Nicolas Dichtel
2016-11-04 9:07 ` Florian Westphal [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=20161104090726.GA16482@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.