From: Florian Westphal <fw@strlen.de>
To: Roi Dayan <roid@nvidia.com>
Cc: Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netdev@vger.kernel.org, Paul Blakey <paulb@nvidia.com>,
Oz Shlomo <ozsh@nvidia.com>
Subject: Re: [PATCH net 1/1] netfilter: conntrack: Check offload bit on table dump
Date: Mon, 1 Feb 2021 16:25:34 +0100 [thread overview]
Message-ID: <20210201152534.GJ12443@breakpoint.cc> (raw)
In-Reply-To: <edb8da93-d859-e7ae-53dd-cae09dff2eba@nvidia.com>
Roi Dayan <roid@nvidia.com> wrote:
> > TCP initial timeout is one minute, UDP 30 seconds.
> > That should surely be enough to do flow_offload_add (which extends
> > the timeout)?
>
> Yes, flow_offload_add() extends the timeout. but it needs to finish.
>
> >
> > Maybe something is doing flow_offload_add() for unconfirmed conntrack?
> >
> > In unconfirmed conntrack case, ct->timeout is absolute timeout value, e.g. for
> > tcp it will be set to 60 * HZ.
>
> When I hit the issue I printed jiffies and ct->timeout and saw they are
> the same or very close but not an absolute number.
Thats strange, for new flows they should not be close at all.
UDP sets a 30 second timeout, TCP sets a 60 second initial timeout.
Do you think rhashtable_insert_fast() in flow_offload_add() blocks for
dozens of seconds?
Thats about the only thing I can see between 'offload bit gets set'
and 'timeout is extended' in flow_offload_add() that could at least
spend *some* time.
> We hit this issue before more easily and pushed this fix
>
> 4203b19c2796 netfilter: flowtable: Set offload timeout when adding flow
This fix makes sense to me.
next prev parent reply other threads:[~2021-02-01 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:40 [PATCH net 1/1] netfilter: conntrack: Check offload bit on table dump Roi Dayan
2021-01-30 12:01 ` Pablo Neira Ayuso
[not found] ` <3a29e9b5-7bf8-5c00-3ede-738f9b4725bf@nvidia.com>
[not found] ` <997cbda4-acd1-a000-1408-269bc5c3abf3@nvidia.com>
2021-02-01 3:08 ` Pablo Neira Ayuso
2021-02-01 7:53 ` Roi Dayan
2021-02-01 11:50 ` Florian Westphal
2021-02-01 15:04 ` Roi Dayan
2021-02-01 15:25 ` Florian Westphal [this message]
2021-02-02 17:08 ` Roi Dayan
2021-02-03 12:50 ` Florian Westphal
2021-02-07 8:38 ` Roi Dayan
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=20210201152534.GJ12443@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=pablo@netfilter.org \
--cc=paulb@nvidia.com \
--cc=roid@nvidia.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.