DPDK usage discussions
 help / color / mirror / Atom feed
From: Anshu Boonapalli <anshu.boonapalli@gmail.com>
To: barbette@kth.se
Cc: users@dpdk.org
Subject: Re: [dpdk-users] MLX5 Rx HW Timestamp units
Date: Thu, 29 Nov 2018 06:24:11 -0700	[thread overview]
Message-ID: <CA+=pU-KqhEBC20D270M=1ELGKrMzvXGhrd_2HCR2=VajBV2+gQ@mail.gmail.com> (raw)
In-Reply-To: <1543399262203.78098@kth.se>

Thank you very much Tom!

Do you know if your work is portable to DPDK 17.11 tip? If not, i will look
into the move to 18.11.

-Anshu

On Wed, Nov 28, 2018 at 3:01 AM Tom Barbette <barbette@kth.se> wrote:

> You actually motivated me to finish re-writing the patch... I just sent it
> to the dev mailing list. You'll also find the 3 commits there :
> https://github.com/tbarbette/dpdk/tree/mlxclock
>
>
> Tom
> ------------------------------
> *De :* Anshu Boonapalli <anshu.boonapalli@gmail.com>
> *Envoyé :* mardi 27 novembre 2018 16:36
> *À :* Tom Barbette
> *Cc :* users@dpdk.org
> *Objet :* Re: [dpdk-users] MLX5 Rx HW Timestamp units
>
> hi Tom,
>
> Thanks for clarifying.
>
> I am interested in the patch that allows the query of the current device
> clock values. Please point me to this patch.
>
> -Anshu
>
> On Tue, Nov 27, 2018 at 12:57 AM Tom Barbette <barbette@kth.se> wrote:
>
>> Hi Anshu,
>>
>> No it's the value of an internal Clock. The frequency and the base are
>> both unknown.
>>
>> We have a patch that works (but must be reworked before submission to
>> dev) that allows to query the current device clock value. Then from there
>> you can derive the base and the frequency. I can send it to you if you wish.
>>
>> Tom
>> ________________________________________
>> De : users <users-bounces@dpdk.org> de la part de Anshu Boonapalli <
>> anshu.boonapalli@gmail.com>
>> Envoyé : mardi 27 novembre 2018 02:41
>> À : users@dpdk.org
>> Objet : [dpdk-users] MLX5 Rx HW Timestamp units
>>
>> Anyone know the units of Rx HW timestamps MLX5 provides?
>>
>> I assumed nanoseconds but tests i have run don't match the nanosecond
>> units.
>>
>> Thanks,
>> -Anshu
>>
>

      reply	other threads:[~2018-11-29 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  1:41 Anshu Boonapalli
2018-11-27  7:57 ` Tom Barbette
2018-11-27 15:36   ` Anshu Boonapalli
2018-11-28 10:01     ` Tom Barbette
2018-11-29 13:24       ` Anshu Boonapalli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+=pU-KqhEBC20D270M=1ELGKrMzvXGhrd_2HCR2=VajBV2+gQ@mail.gmail.com' \
    --to=anshu.boonapalli@gmail.com \
    --cc=barbette@kth.se \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).