From: Ralf Grosse Boerger <ralfgb@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Kernel NIC Interface and SO_TIMESTAMPING/PTP Hardware Clock
Date: Wed, 9 Mar 2016 16:36:51 +0100 [thread overview]
Message-ID: <CAN3415+Hxm6kqFGfBnbNwJ2hXL8_SYmg=Dcq_O8iWm55CGUKVg@mail.gmail.com> (raw)
Hi,
I am planning to use a PTP Daemon (http://linuxptp.sourceforge.net/) on a
Ethernet port that is used by the DPDK.
The kernel NIC interface should allow me to pass PTP frame from/to the
Linux Ethernet interface (via rte_kni_tx_burst() and rte_kni_rx_burst()).
But the PTP daemon also requires SO_TIMESTAMPING/PTP Hardware Clock-API of the
Linux Ethernet device.
If I start the ptp4l daemon on a KNI device (for example vEth0_0) I
get an error that the hardware timestamping mode is not supported.
Can anyone point me to the relevant source files of the KNI driver
that need to be modified to add HW timestamping and PHC support to a
KNI device?
(I am using an Intel i210 card).
Thanks in advance
Ralf
reply other threads:[~2016-03-09 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAN3415+Hxm6kqFGfBnbNwJ2hXL8_SYmg=Dcq_O8iWm55CGUKVg@mail.gmail.com' \
--to=ralfgb@gmail.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).