From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, Nadia Pinaeva <n.m.pinaeva@gmail.com>
Subject: Re: [PATCH nf-next] netfilter: conntrack: add conntrack event timestamp
Date: Thu, 9 Jan 2025 00:48:44 +0100 [thread overview]
Message-ID: <Z38O3LCrBRUDwUMR@calendula> (raw)
In-Reply-To: <Z31OB1LLNA5AEDn1@strlen.de>
On Tue, Jan 07, 2025 at 04:53:43PM +0100, Florian Westphal wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > Nadia Pinaeva writes:
> > I am working on a tool that allows collecting network performance
> > metrics by using conntrack events.
> > Start time of a conntrack entry is used to evaluate seen_reply
> > latency, therefore the sooner it is timestamped, the better the
> > precision is.
> > In particular, when using this tool to compare the performance of the
> > same feature implemented using iptables/nftables/OVS it is crucial
> > to have the entry timestamped earlier to see any difference.
> >
> > At this time, conntrack events can only get timestamped at recv time in
> > userspace, so there can be some delay between the event being generated
> > and the userspace process consuming the message.
>
> Ping, should I resend this patch?
For some reason I considered this was waiting for Nadia's feedback and
I don't remember to have see an acknowledgment on this. I assume then
this is good enough for the measurements that are needed.
This is enabled via the ktimestamp toggle, so there is no new toggle
as you suggested.
Patch LGTM.
Will you follow up with userspace updates for this new code?
Thanks.
next prev parent reply other threads:[~2025-01-08 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 13:46 [PATCH nf-next] netfilter: conntrack: add conntrack event timestamp Florian Westphal
2025-01-07 15:53 ` Florian Westphal
2025-01-08 23:48 ` Pablo Neira Ayuso [this message]
2025-01-09 0:31 ` Florian Westphal
2025-01-09 10:25 ` Antonio Ojea
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 19:41 Florian Westphal
2024-11-08 0:09 ` kernel test robot
2024-11-08 1:33 ` kernel test robot
2024-11-08 6:34 ` kernel test robot
2024-11-12 18:25 ` 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=Z38O3LCrBRUDwUMR@calendula \
--to=pablo@netfilter.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox