Home
last modified time | relevance | path

Searched refs:timestamps (Results 1 – 25 of 50) sorted by relevance

12

/Linux-v4.19/Documentation/networking/
Dtimestamping.txt4 The interfaces for receiving network packages timestamps are:
20 Generates timestamps on reception, transmission or both. Supports
22 timestamps for stream sockets.
38 Its struct timespec allows for higher resolution (ns) timestamps than the
60 Some bits are requests to the stack to try to generate timestamps. Any
63 is possible to selectively request timestamps for a subset of packets
71 Request rx timestamps generated by the network adapter.
74 Request rx timestamps when data enters the kernel. These timestamps
79 Request tx timestamps generated by the network adapter. This flag
83 Request tx timestamps when data leaves the kernel. These timestamps
[all …]
Dpacket_mmap.txt205 related meta-information like timestamps without requiring a system call.
1007 hardware timestamps to be used. Note: you may need to enable the generation
1008 of hardware timestamps with SIOCSHWTSTAMP (see related information from
1016 For the mmap(2)ed ring buffers, such timestamps are stored in the
1029 Getting timestamps for the TX_RING works as follows: i) fill the ring frames,
1032 through the frames to pick up the individual hw/sw timestamps.
1047 for more information on hardware timestamps.
/Linux-v4.19/Documentation/sound/designs/
Dtimestamping.rst5 The ALSA API can provide two different system timestamps:
23 timestamps allow for applications to keep track of the 'fullness' of
33 When timestamps are enabled, the avail/delay information is reported
111 counter-intuitively not increase the precision of timestamps, e.g. if a
129 timestamps from hardware registers or from IPC takes time, the more
130 timestamps are read the more imprecise the combined measurements
132 timestamp is reported. Applications that need different timestamps
185 error. In example 3 where the timestamps are measured with the link
186 wallclock, the timestamps show a monotonic behavior and a lower
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-ptp91 timestamps. To enable external timestamps, write the
93 To disable external timestamps, write the channel
100 This file provides timestamps on external events, in
/Linux-v4.19/drivers/net/ethernet/sfc/
Dptp.c1078 struct skb_shared_hwtstamps timestamps; in efx_ptp_xmit_skb_mc() local
1107 memset(&timestamps, 0, sizeof(timestamps)); in efx_ptp_xmit_skb_mc()
1108 timestamps.hwtstamp = ptp_data->nic_to_kernel_time( in efx_ptp_xmit_skb_mc()
1113 skb_tstamp_tx(skb, &timestamps); in efx_ptp_xmit_skb_mc()
1178 struct skb_shared_hwtstamps *timestamps; in efx_ptp_match_rx() local
1181 timestamps = skb_hwtstamps(skb); in efx_ptp_match_rx()
1182 timestamps->hwtstamp = evt->hwtimestamp; in efx_ptp_match_rx()
1981 struct skb_shared_hwtstamps *timestamps; in __efx_rx_skb_attach_timestamp() local
2024 timestamps = skb_hwtstamps(skb); in __efx_rx_skb_attach_timestamp()
2025 timestamps->hwtstamp = in __efx_rx_skb_attach_timestamp()
/Linux-v4.19/Documentation/core-api/
Dtimekeeping.rst20 Useful for reliable timestamps and measuring short time intervals
37 user space. This is used for all timestamps that need to
122 but can't easily use 'jiffies', e.g. for inode timestamps.
/Linux-v4.19/Documentation/media/uapi/v4l/
Dstreaming-par.rst18 not augmented by timestamps or sequence counters, and to avoid
Dpixfmt-meta-uvc.rst18 timing information, required for precise interpretation of timestamps, contained
Drw.rst19 counters or timestamps are passed. This information is necessary to
Dvidioc-g-parm.rst42 :ref:`write() <func-write>`, which are not augmented by timestamps or sequence
167 :ref:`write() <func-write>` mode (in streaming mode timestamps
/Linux-v4.19/Documentation/filesystems/
Dcramfs.txt35 No timestamps are stored in a cramfs, so these default to the epoch
36 (1970 GMT). Recently-accessed files may have updated timestamps, but
/Linux-v4.19/Documentation/fmc/
Dparameters.txt42 golden gateware for the SPEC card, removing the leading timestamps to
/Linux-v4.19/tools/power/pm-graph/config/
Dfreeze.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dstandby.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dfreeze-callgraph.cfg89 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dfreeze-dev.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dstandby-callgraph.cfg89 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-dev.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-x2-proc.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dstandby-dev.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend-callgraph.cfg93 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
Dsuspend.cfg88 # Number of significant digits in timestamps (0:S, [3:ms], 6:us)
/Linux-v4.19/fs/cramfs/
DKconfig9 16/32 bits uid/gid, hard links and timestamps.
/Linux-v4.19/drivers/media/rc/img-ir/
DKconfig16 less reliable (due to lack of timestamps) and consumes more
/Linux-v4.19/Documentation/sysctl/
Dnet.txt176 Allow processes to receive tx timestamps looped together with the original
261 If set to 0, RX packet timestamps can be sampled after RPS processing, when
262 the target CPU processes packets. It might give some delay on timestamps, but
265 If set to 1 (default), timestamps are sampled as soon as possible, before

12