DPDK patches and discussions
 help / color / mirror / Atom feed
From: John McNamara <john.mcnamara@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 0/7] ethdev: add support for ieee1588 timestamping
Date: Thu,  9 Jul 2015 14:30:13 +0100	[thread overview]
Message-ID: <1436448620-13972-1-git-send-email-john.mcnamara@intel.com> (raw)

This patchset adds ethdev API to enable and read IEEE1588/802.1AS PTP
timestamps from devices that support it. The following functions are added:

    rte_eth_timesync_enable()
    rte_eth_timesync_disable()
    rte_eth_timesync_read_rx_timestamp()
    rte_eth_timesync_read_tx_timestamp()

The "ieee1588" forwarding mode in testpmd is also refactored to demonstrate
the new API and to clean up the code.

Adds support for igb, ixgbe and i40e.

V4:
* Added timesync field to end of mbuf to pass IEEE1588 registers and flags.
  Removed previous ABI deprecation notice.

V3:
* Fixed issued with version.map.

V2:
* Added i40e support.

* Renamed ethdev functions from rte_eth_ieee15888_*() to rte_eth_timesync_*()
  since 802.1AS can be supported through the same interfaces.

V1:
* Initial version for igb and ixgbe.


John McNamara (7):
  ethdev: add support for ieee1588 timestamping
  mbuf: add field for ieee1588 timesync index
  e1000: add support for ieee1588 timestamping
  ixgbe: add support for ieee1588 timestamping
  i40e: add support for ieee1588 timestamping
  app/testpmd: refactor ieee1588 forwarding
  doc: document ieee1588 forwarding mode

 app/test-pmd/ieee1588fwd.c                  | 466 ++--------------------------
 doc/guides/testpmd_app_ug/run_app.rst       |   2 +-
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |   2 +
 drivers/net/e1000/igb_ethdev.c              | 115 +++++++
 drivers/net/i40e/i40e_ethdev.c              | 143 +++++++++
 drivers/net/i40e/i40e_rxtx.c                |  40 ++-
 drivers/net/ixgbe/ixgbe_ethdev.c            | 122 ++++++++
 lib/librte_ether/rte_ethdev.c               |  70 ++++-
 lib/librte_ether/rte_ethdev.h               |  90 +++++-
 lib/librte_ether/rte_ether_version.map      |   4 +
 lib/librte_mbuf/rte_mbuf.h                  |   3 +
 11 files changed, 614 insertions(+), 443 deletions(-)

--
1.8.1.4

             reply	other threads:[~2015-07-09 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 13:30 John McNamara [this message]
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 1/7] " John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 2/7] mbuf: add field for ieee1588 timesync index John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 3/7] e1000: add support for ieee1588 timestamping John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 4/7] ixgbe: " John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 5/7] i40e: " John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 6/7] app/testpmd: refactor ieee1588 forwarding John McNamara
2015-07-09 13:30 ` [dpdk-dev] [PATCH v4 7/7] doc: document ieee1588 forwarding mode John McNamara
2015-07-10  0:43 ` [dpdk-dev] [PATCH v4 0/7] ethdev: add support for ieee1588 timestamping Thomas Monjalon

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=1436448620-13972-1-git-send-email-john.mcnamara@intel.com \
    --to=john.mcnamara@intel.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).