diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2009-02-12 05:03:36 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2009-02-15 22:43:33 -0800 |
| commit | cb9eff097831007afb30d64373f29d99825d0068 (patch) | |
| tree | 823a5668c6f4b3f577a1d4cc73b3df2d7e33c5c4 /include/asm-frv | |
| parent | a75244c3d519fcb490ca2bf3f123c98017f1e8d0 (diff) | |
| download | linux-3.10-cb9eff097831007afb30d64373f29d99825d0068.tar.gz linux-3.10-cb9eff097831007afb30d64373f29d99825d0068.tar.bz2 linux-3.10-cb9eff097831007afb30d64373f29d99825d0068.zip | |
net: new user space API for time stamping of incoming and outgoing packets
User space can request hardware and/or software time stamping.
Reporting of the result(s) via a new control message is enabled
separately for each field in the message because some of the
fields may require additional computation and thus cause overhead.
User space can tell the different kinds of time stamps apart
and choose what suits its needs.
When a TX timestamp operation is requested, the TX skb will be cloned
and the clone will be time stamped (in hardware or software) and added
to the socket error queue of the skb, if the skb has a socket
associated with it.
The actual TX timestamp will reach userspace as a RX timestamp on the
cloned packet. If timestamping is requested and no timestamping is
done in the device driver (potentially this may use hardware
timestamping), it will be done in software after the device's
start_hard_xmit routine.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/asm-frv')
| -rw-r--r-- | include/asm-frv/socket.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/asm-frv/socket.h b/include/asm-frv/socket.h index e51ca67b935..57c3d4054e8 100644 --- a/include/asm-frv/socket.h +++ b/include/asm-frv/socket.h @@ -54,5 +54,8 @@ #define SO_MARK 36 +#define SO_TIMESTAMPING 37 +#define SCM_TIMESTAMPING SO_TIMESTAMPING + #endif /* _ASM_SOCKET_H */ |