netdev - Re: [RFC][PATCH 1/1] net: support for hardware timestamping

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: <200807301134.49978.netdev@axxeo.de>
Date:	Wed, 30 Jul 2008 11:34:49 +0200
From:	Ingo Oeser <netdev@...eo.de>
To:	Patrick Ohly <patrick.ohly@...el.com>
Cc:	Octavian Purdila <opurdila@...acom.com>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: [RFC][PATCH 1/1] net: support for hardware timestamping

Hi Patrick,

Patrick Ohly schrieb:
> Perhaps the parameter of the new
> SO_TXTIMESTAMP can be a multi-value? 0 = no TX time stamps, 1 = TX time
> stamp in hardware if possible with software as fallback, 2 = only
> hardware TX time stamps. Either that, or use the same new socket flag as
> for RX time stamps.

Perhaps we can make it a bitmask (please choose a good prefix instead of XXX):

enum {
	XXX_SOFTWARE_TX_TIMESTAMP = (1 << 0),
	XXX_SOFTWARE_RX_TIMESTAMP = (1 << 1),
	XXX_DRIVER_TX_TIMESTAMP	  = (1 << 2),
	XXX_DRIVER_RX_TIMESTAMP	  = (1 << 3),
};

That way we can express everything required so far and have some bits left 
to define precision, system time correlation and more.


Best Regards

Ingo Oeser
--
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