From: "科来 谭春海" <chunhai.tan@colasoft.com.cn>
To: "'Keunhong Lee'" <dlrmsghd@gmail.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] 答复: How to set timestamp in 82599 NICs in DPDK?
Date: Mon, 1 Jun 2015 14:39:11 +0800 [thread overview]
Message-ID: <004d01d09c35$abd42070$037c6150$@colasoft.com.cn> (raw)
In-Reply-To: <CAKBXKmBAM4Y=ban8g+x05qEeHCF2M+g4c3eU97zvG3JT7NE2AA@mail.gmail.com>
Hi Keunhong,
Thanks for your response. Seems ixgbe only supports hw timestamping for PTP packets. But I still don’t understand why igb and e1000 support hw timestamping all packets while ixgbe does not.
发件人: Keunhong Lee [mailto:dlrmsghd@gmail.com]
发送时间: 2015年6月1日 11:51
收件人: 科来 谭春海
抄送: dev@dpdk.org
主题: Re: [dpdk-dev] How to set timestamp in 82599 NICs in DPDK?
http://dpdk.org/browse/dpdk/tree/app/test-pmd/ieee1588fwd.c
This code example contains enabling PTP with intel NICs.
Keunhong.
2015-06-01 12:48 GMT+09:00 Keunhong Lee <dlrmsghd@gmail.com>:
82599 supports hw timestamping for PTP packets.
I don't know whether it supports timestamping for general packets.
http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L640
says that
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L640> 640 default:
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L641> 641 /*
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L642> 642 * register RXMTRL must be set in order to do V1 packets,
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L643> 643 * therefore it is not possible to time stamp both V1 Sync and
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L644> 644 * Delay_Req messages and hardware does not support
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L645> 645 * timestamping all packets => return error
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L646> 646 */
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L647> 647 <http://lxr.free-electrons.com/ident?i=config> config->rx_filter = HWTSTAMP_FILTER_NONE;
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L648> 648 return - <http://lxr.free-electrons.com/ident?i=ERANGE> ERANGE;
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c#L649> 649 }
Keunhong.
2015-06-01 11:38 GMT+09:00 科来 谭春海 <chunhai.tan@colasoft.com.cn>:
Hi
I noticed that there is a patch which can set hardware timestamp for the
received
packets(http://www.wand.net.nz/trac/libtrace/browser/Intel%20DPDK%20Patches/ <http://www.wand.net.nz/trac/libtrace/browser/Intel%20DPDK%20Patches/hardware_timestamp.patch?rev=ce7153dbc6a13c18bf8033af08c1249527754168>
hardware_timestamp.patch?rev=ce7153dbc6a13c18bf8033af08c1249527754168), but
it only works in e1000 and igb NICs. I want to capture packets with
timestamp info in 82599 NICs, what should I do? Could you give me some help?
Thanks.
Chunhai Tan
prev parent reply other threads:[~2015-06-01 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 2:38 [dpdk-dev] " 科来 谭春海
2015-06-01 3:48 ` Keunhong Lee
2015-06-01 3:51 ` Keunhong Lee
2015-06-01 6:39 ` 科来 谭春海 [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='004d01d09c35$abd42070$037c6150$@colasoft.com.cn' \
--to=chunhai.tan@colasoft.com.cn \
--cc=dev@dpdk.org \
--cc=dlrmsghd@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).