Searched refs:took (Results 1 – 10 of 10) sorted by relevance
33 The TX time tells how long it took for network packet from its creation to54 took for a network packet to go from previous state to next.60 * Packet is about to be placed to transmit queue. The time it took from network63 queue. It took **15** microseconds from previous state.65 network packet. It took **23** microseconds from previous state.66 * In total it took on average **60** microseconds to get the network packet74 * Packet is about to be placed to receive queue. The time it took from network77 queue. It took **6** microseconds from previous state.79 It took **11** microseconds from previous state.80 * The last value tells how long it took from there to the application. Here[all …]
17 it took to deliver the network packet, and the network interface, priority
25 processors vs. other architectures, the sample outputs the time and number of cycles it took to50 The sample will output the number of cycles it took to compute the moving averages, as well as the
37 # when an unknown printer took a galley of type and scrambled it to make a type specimen book.45 when an unknown printer took a galley of type and scrambled it to make a type specimen book.
13 * A ``nanoappHandleEvent`` function used to notify the nanoapp tha an event of interest took place.
33 - :file:`math_ops.c`: executes the math functions, computes the cycles it took to execute and check…
176 :ref:`install_py_requirements` step you took in the getting started
287 simulated time when the last clock ratio adjustment took place.
327 * Added support for getting statistics about the time it took to receive or send
1569 # on Windows. In the beginning of 2021 Microsoft took the original page, with
