netdev - [rfc] new sk_buff member: hwstamp

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-next>] [day] [month] [year] [list]

Message-Id: <200807141843.00845.opurdila@ixiacom.com>
Date:	Mon, 14 Jul 2008 18:43:00 +0300
From:	Octavian Purdila <opurdila@...acom.com>
To:	netdev@...r.kernel.org
Subject: [rfc] new sk_buff member: hwstamp

Hi everybody,

In our Linux port we added a new sk_buff member, hwstamp, to store a hardware 
generated timestamp for received packets. The hardware can also insert  
hardware timestamps in the payload on the TX path and can have the RX / TX 
clocks synchronized. We use this infrastructure to compute one-way delays 
with high precision (20ns resolution).

I know that adding new members to such heavily used structures like the skb is 
viewed harshly - especially for such exotic cases as the one described above. 
So, would such a patch be considered for inclusion? Or maybe there is a 
better way of doing the above?

Thanks,
tavi
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html