netdev - Re: [PATCH net-next 08/12] net: homa: create homa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <471a65c1-2ddd-4dc3-a241-fd5bdf28ce55@lunn.ch>
Date: Wed, 30 Oct 2024 14:06:32 +0100
From: Andrew Lunn <andrew@...n.ch>
To: John Ousterhout <ouster@...stanford.edu>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 08/12] net: homa: create homa_incoming.c

> BTW, I did some experiments with tracepoints to see if they could
> replace timetraces. Unfortunately, the basic latency for a tracepoint
> is about 100-200 ns, whereas for tt_record it's about 8-10 ns.

This is good to know, and you will need it for justification if you
decide to try to get tt_record merged.

However, once you get homa merged, you will find it easier to reach
out to the tracepoint Maintainers and talk about the issues you
have. If working together you can make tracepoints a lot faster,
everybody benefits.

	Andrew