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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAGXJAmw0vu5dFa1YeRqGbed8gmyNtSSEQk_jZx3M4_q=_xHxkA@mail.gmail.com>
Date: Wed, 30 Oct 2024 08:49:46 -0700
From: John Ousterhout <ouster@...stanford.edu>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 08/12] net: homa: create homa_incoming.c

On Wed, Oct 30, 2024 at 6:06 AM Andrew Lunn <andrew@...n.ch> wrote:
>
> > 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.

Agreed.

-John-