Thursday, September 6, 2018 12:33 PM, Tom Barbette:
Subject: RE: MLX5 should define the timestamp field in the doc
>
>It's true that it is a little bit a distortion of the original purpose. Here I
>want to query the time from the device (ie, the device's current clock). Maybe
>a new function in t
It's true that it is a little bit a distortion of the original purpose. Here I
want to query the time from the device (ie, the device's current clock). Maybe
a new function in the API would be more suited? CCing Thomas Mojalon for that
part of the discussion.
I guess there is a case to query
Wednesday, September 5, 2018 12:00 PM, Tom Barbette:
>Actually I managed this patch to implement support for
>rte_eth_timesync_read_time.
I am not fully familiar w/ this API, but it looks like the timespec returned
from this call is expected to be in real time values (i.e. seconds and nano
seco
Actually I managed this patch to implement support for
rte_eth_timesync_read_time.
Please tell me potential modifications, and if I shall submit it again as a
"normal" patch to dev ?
---
drivers/net/mlx5/mlx5.c| 1 +
drivers/net/mlx5/mlx5.h| 1 +
drivers/net/mlx5/mlx5_ethde
Thanks for the details.
The use case is clear. We will take it internally to see when we can support it.
AFAIK we cannot read the internal time from userspace.
Adding also AlexR to comment
From: Tom Barbette
Sent: Wednesday, September 5, 2018 10:11 AM
To: Shahaf Shuler ; dev@dpdk.org
Cc: Yongse
Thanks for your answer Shahaf !
We're trying to measure the latency of packets going through various service
chains inside individual "server". Eg. we can see that on Server 1, the
latency for the service chain handling HTTP packets is ~800ns (+ max and mins,
tail latency, etc). What we do no
Hi Tom,
Tuesday, September 4, 2018 5:26 PM, Tom Barbette:
>
>Hi all,
>
>As far as I know, MLX5 is the only driver to support hardware timestamping.
>
>It would be great to update the doc to explain what the hardware timestamp is
>supposed to be.
We probably need to update the doc, but the
Hi all,
As far as I know, MLX5 is the only driver to support hardware timestamping.
It would be great to update the doc to explain what the hardware timestamp is
supposed to be. If it's nanoseconds, then just a shift regarding system time is
enough ? Does it also need a multiplication? Can we
8 matches
Mail list logo
