netdev - Re: [RFC bpf-next v2 06/11] net: veth: Implement devtx timestamp kfuncs

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]

Date: Fri, 23 Jun 2023 16:29:29 -0700
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: Stanislav Fomichev <sdf@...gle.com>, bpf@...r.kernel.org
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
 martin.lau@...ux.dev, song@...nel.org, yhs@...com,
 john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
 haoluo@...gle.com, jolsa@...nel.org, netdev@...r.kernel.org
Subject: Re: [RFC bpf-next v2 06/11] net: veth: Implement devtx timestamp
 kfuncs

Stanislav Fomichev <sdf@...gle.com> writes:

> Have a software-based example for kfuncs to showcase how it
> can be used in the real devices and to have something to
> test against in the selftests.
>
> Both path (skb & xdp) are covered. Only the skb path is really
> tested though.
>
> Cc: netdev@...r.kernel.org
> Signed-off-by: Stanislav Fomichev <sdf@...gle.com>

Not really related to this patch, but to how it would work with
different drivers/hardware.

In some of our hardware (the ones handled by igc/igb, for example), the
timestamp notification comes some time after the transmit completion
event.

>From what I could gather, the idea would be for the driver to "hold" the
completion until the timestamp is ready and then signal the completion
of the frame. Is that right?


Cheers,
-- 
Vinicius