Home
last modified time | relevance | path

Searched refs:SCM_TSTAMP_SCHED (Results 1 – 9 of 9) sorted by relevance

/linux/tools/testing/selftests/net/packetdrill/
H A Dtcp_timestamping_server.pkt40 // SCM_TSTAMP_SCHED for the first chunk should be received almost immediately
55 ee_info=SCM_TSTAMP_SCHED,
76 // SCM_TSTAMP_SCHED for the second chunk should be received almost immediately
91 ee_info=SCM_TSTAMP_SCHED,
H A Dtcp_timestamping_client-only-last-byte.pkt37 // SCM_TSTAMP_SCHED for the last byte should be received almost immediately
55 ee_info=SCM_TSTAMP_SCHED,
H A Dtcp_timestamping_partial.pkt38 // SCM_TSTAMP_SCHED for the first chunk should be received almost immediately
53 ee_info=SCM_TSTAMP_SCHED,
/linux/include/uapi/linux/
H A Derrqueue.h74 SCM_TSTAMP_SCHED, /* data entered the packet scheduler */ enumerator
/linux/tools/testing/selftests/bpf/prog_tests/
H A Dnet_timestamping.c30 if (tstype == SCM_TSTAMP_SCHED) in validate_key()
56 case SCM_TSTAMP_SCHED: in test_socket_timestamp()
137 ASSERT_EQ(SK_TS_SCHED, 1, "SCM_TSTAMP_SCHED"); in test_socket_timestamping()
/linux/tools/testing/selftests/net/
H A Dcmsg_sender.c336 [SCM_TSTAMP_SCHED] = "SCHED", in cs_ts_info2str()
H A Dtxtimestamp.c225 case SCM_TSTAMP_SCHED: in print_timestamp()
/linux/Documentation/networking/
H A Dj1939.rst705 - ``SCM_TSTAMP_SCHED``: This timestamp is valid for Extended Transport
783 - It is typically paired with a corresponding ``SCM_TSTAMP_SCHED`` event
848 scheduled for transmission (``SCM_TSTAMP_SCHED``).
/linux/net/core/
H A Ddev.c4633 __skb_tstamp_tx(skb, NULL, NULL, skb->sk, SCM_TSTAMP_SCHED); in __dev_queue_xmit()