netdev - Re: Problems obtaining software TX timestamps

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: <20100908.142401.233712108.davem@davemloft.net>
Date:	Wed, 08 Sep 2010 14:24:01 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ikofler@....uni-klu.ac.at
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: Problems obtaining software TX timestamps

From: Ingo Kofler <ikofler@....uni-klu.ac.at>
Date: Wed, 08 Sep 2010 23:21:36 +0200

> Ok, for hardware timestamps it seems logically for me that the driver
> has to support this. But what about the software timestamps - do they
> also require support from the driver? Is there no generic
> implementation in the networking stack?

Each and every driver must add the hook because it must be inside of
the driver's transmit function due to packet lifetime issues etc.
--
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