From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Nadia Pinaeva <n.m.pinaeva@gmail.com>,
netfilter-devel@vger.kernel.org,
Antonio Ojea <antonio.ojea.garcia@gmail.com>
Subject: Re: [PATCH nf-next v2] netfilter: conntrack: collect start time as early as possible
Date: Tue, 5 Nov 2024 17:45:15 +0100 [thread overview]
Message-ID: <ZypLmxmAb_Hp2HBS@calendula> (raw)
In-Reply-To: <20241105163308.GA9779@breakpoint.cc>
On Tue, Nov 05, 2024 at 05:33:08PM +0100, Florian Westphal wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > It will help for SEEN_REPLY. But I don't see how it will avoid this
> > > patch.
> >
> > Not current time from ctnetlink, but use the ecache extension to store
> > the timestamp when the conntrack is allocated, ecache is already
> > initialized from init_conntrack() path.
>
> OK, so we do ktime_get_real() twice.
> I think its way worse than this proposal, but okay.
My proposal is to add more well-known "fixed points" to get numbers.
At this stage, there is start= and stop= ktimestamps, where start=
represents insertion to hashes (confirmation time). I think this adds
more ktimestamp point that can be enabled to collect numbers in an
optional fashion, both two timestamps do not need to be turned on
necessarily.
> I'll work on this.
Thanks, I'd rather convince you this is the way to go, if after
quickly sketching a patchset you think it is not worth for more
reasons, we can revisit.
next prev parent reply other threads:[~2024-11-05 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 13:12 [PATCH nf-next v2] netfilter: conntrack: collect start time as early as possible Florian Westphal
2024-11-03 10:26 ` Nadia Pinaeva
2024-11-04 9:09 ` Pablo Neira Ayuso
2024-11-04 9:39 ` Florian Westphal
2024-11-04 10:03 ` Nadia Pinaeva
2024-11-04 11:09 ` Antonio Ojea
2024-11-05 16:08 ` Pablo Neira Ayuso
2024-11-05 16:23 ` Florian Westphal
2024-11-05 16:28 ` Pablo Neira Ayuso
2024-11-05 16:33 ` Florian Westphal
2024-11-05 16:45 ` Pablo Neira Ayuso [this message]
2024-11-05 17:32 ` Florian Westphal
2024-11-05 23:20 ` Pablo Neira Ayuso
2024-11-06 8:26 ` Florian Westphal
2024-11-06 8:32 ` Pablo Neira Ayuso
2024-11-06 8:34 ` Florian Westphal
2024-11-06 9:10 ` Pablo Neira Ayuso
2024-11-06 12:39 ` Florian Westphal
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=ZypLmxmAb_Hp2HBS@calendula \
--to=pablo@netfilter.org \
--cc=antonio.ojea.garcia@gmail.com \
--cc=fw@strlen.de \
--cc=n.m.pinaeva@gmail.com \
--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 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.