From: Paul Emmerich <emmericp@net.in.tum.de>
To: Nishant Verma <vnish11@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] PTP IXGBEVF
Date: Fri, 6 Jul 2018 19:33:35 +0200 [thread overview]
Message-ID: <B1BDBBB7-8F30-4412-B788-7ACC7A3D9BC9@net.in.tum.de> (raw)
In-Reply-To: <CAHhCjUFS2tRPhb7BSNd+4sovthPW6QPwjyYomQigfDSdRTHGJA@mail.gmail.com>
The hardware doesn't support PTP on VFs.
Paul
> Am 06.07.2018 um 18:34 schrieb Nishant Verma <vnish11@gmail.com>:
>
> Hi All,
>
> My IXGBEVF info is as follows:
> filename:
> /lib/modules/3.10.0-514.el7.x86_64/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko
> version: 4.3.5
> license: GPL
> description: Intel(R) 10 Gigabit Virtual Function Network Driver
> author: Intel Corporation, <linux.nics@intel.com>
> rhelversion: 7.3
>
> But the PTP Hardware clock is not enabled on vf's created by SR-IOV.
>
> Is there any way to enable that?
>
> Below is the properties of the physical and virtual network interface.
>
> *PHYSICAL*:ethtool -T eno2
> Time stamping parameters for eno2:
> Capabilities:
> hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
> software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
> hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
> software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
> software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
> hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
> PTP Hardware Clock: 1
> Hardware Transmit Timestamp Modes:
> off (HWTSTAMP_TX_OFF)
> on (HWTSTAMP_TX_ON)
> Hardware Receive Filter Modes:
> none (HWTSTAMP_FILTER_NONE)
> all (HWTSTAMP_FILTER_ALL)
> ptpv1-l4-sync (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)
> ptpv1-l4-delay-req (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)
> ptpv2-l4-event (HWTSTAMP_FILTER_PTP_V2_L4_EVENT)
> ptpv2-l4-sync (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)
> ptpv2-l4-delay-req (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)
> ptpv2-l2-event (HWTSTAMP_FILTER_PTP_V2_L2_EVENT)
> ptpv2-l2-sync (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)
> ptpv2-l2-delay-req (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)
> ptpv2-event (HWTSTAMP_FILTER_PTP_V2_EVENT)
> ptpv2-sync (HWTSTAMP_FILTER_PTP_V2_SYNC)
> ptpv2-delay-req (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ)
>
>
>
> * VIRTUAL*:
>
> ethtool -T enp2s16f1
> Time stamping parameters for enp2s16f1:
> Capabilities:
> software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
> software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
> software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
> PTP Hardware Clock: none
> Hardware Transmit Timestamp Modes: none
> Hardware Receive Filter Modes: none
>
>
>
>
> --
> Rgds,
> Nishant
--
Chair of Network Architectures and Services
Department of Informatics
Technical University of Munich
Boltzmannstr. 3
85748 Garching bei München, Germany
prev parent reply other threads:[~2018-07-06 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 16:34 Nishant Verma
2018-07-06 17:33 ` Paul Emmerich [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=B1BDBBB7-8F30-4412-B788-7ACC7A3D9BC9@net.in.tum.de \
--to=emmericp@net.in.tum.de \
--cc=users@dpdk.org \
--cc=vnish11@gmail.com \
/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).