From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, nicolas.dichtel@6wind.com
Subject: Re: [PATCH nf] netfilter: conntrack: refine gc worker heuristics
Date: Tue, 1 Nov 2016 22:53:11 +0100 [thread overview]
Message-ID: <20161101215311.GA17689@breakpoint.cc> (raw)
In-Reply-To: <1478033811.7065.357.camel@edumazet-glaptop3.roam.corp.google.com>
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Tue, 2016-11-01 at 21:01 +0100, Florian Westphal wrote:
> > schedule_delayed_work(&gc_work->dwork, next_run);
>
>
> > @@ -993,6 +1029,7 @@ static void gc_worker(struct work_struct *work)
> > static void conntrack_gc_work_init(struct conntrack_gc_work *gc_work)
> > {
> > INIT_DELAYED_WORK(&gc_work->dwork, gc_worker);
> > + gc_work->next_gc_run = GC_INTERVAL_MAX;
> > gc_work->exiting = false;
> > }
> >
> > @@ -1885,7 +1922,7 @@ int nf_conntrack_init_start(void)
> > nf_ct_untracked_status_or(IPS_CONFIRMED | IPS_UNTRACKED);
> >
> > conntrack_gc_work_init(&conntrack_gc_work);
> > - schedule_delayed_work(&conntrack_gc_work.dwork, GC_INTERVAL);
> > + schedule_delayed_work(&conntrack_gc_work.dwork, GC_INTERVAL_MAX);
> >
> > return 0;
> >
>
>
> We might use system_long_wq instead of system_wq ?
>
> queue_delayed_work(system_long_wq, ...)
Ok, I will change this for v2, thanks Eric.
prev parent reply other threads:[~2016-11-01 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 20:01 [PATCH nf] netfilter: conntrack: refine gc worker heuristics Florian Westphal
2016-11-01 20:56 ` Eric Dumazet
2016-11-01 21:53 ` 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=20161101215311.GA17689@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric.dumazet@gmail.com \
--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.