From: Nicolas Pernas Maradei <nicolas.pernas.maradei@emutex.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Saving packet timestamp when reading from pcap
Date: Tue, 21 Apr 2015 11:50:52 +0100 [thread overview]
Message-ID: <55362B8C.3030604@emutex.com> (raw)
In-Reply-To: <CAKedurzVNNGiZ_q-mYxRVS-jfW7=bpoTH-vY3gJM3Sk68QZOqQ@mail.gmail.com>
Hi Dor,
What you are looking for seems straight forward to implement and it
should not really affect the driver's performance at all. Even adding
the full timestamp (seconds plus microseconds). However, I don't see too
much people looking for that feature to make it to mainline. I could be
wrong and it's not up to me to decide but I believe it wouldn't add too
much value to the driver itself. It would make your testing easier but
that's all. Maybe encapsulating the feature within #defines?
If you were to read the packets from a pcap file and send them through a
real NIC could you use the NIC's HW timestamp if supported? I'm not
entirely sure about it (maybe someone else could provide more info about
it) but it could solve your problem in a cleaner way.
Nico.
next prev parent reply other threads:[~2015-04-21 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 16:06 Dor Green
2015-04-21 10:50 ` Nicolas Pernas Maradei [this message]
2015-04-21 12:02 ` Dor Green
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=55362B8C.3030604@emutex.com \
--to=nicolas.pernas.maradei@emutex.com \
--cc=dev@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).