From: "Su, Simei" <simei.su@intel.com>
To: Chuanyu Xue <chuanyu.xue@uconn.edu>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: RE: [PATCH] net/e1000: support launchtime feature
Date: Thu, 4 Jan 2024 02:56:41 +0000 [thread overview]
Message-ID: <SA1PR11MB6613E0A06CB069024AF11DB29C67A@SA1PR11MB6613.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240103215215.19140-1-chuanyu.xue@uconn.edu>
Hi Chuanyu,
> -----Original Message-----
> From: Chuanyu Xue <chuanyu.xue@uconn.edu>
> Sent: Thursday, January 4, 2024 5:52 AM
> To: Su, Simei <simei.su@intel.com>
> Cc: Xing, Beilei <beilei.xing@intel.com>; chuanyu.xue@uconn.edu;
> dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Subject: RE: [PATCH] net/e1000: support launchtime feature
>
> Hi, Simei
>
> Thank you for your guidance on how to test this feature.
>
> >> Following is how I try to test with testpmd. Please let me know if I
> >> did something wrong.
> >>
> >> sudo ./dpdk-testpmd -- -i --forward-mode=txonly
> >>
> >> testpmd> port stop 0
> >> testpmd> set burst 1
> >> testpmd> set txtimes 100000000,0
> >> testpmd> port config 0 tx_offload send_on_timestamp on
> >> testpmd> port start 0
> >> testpmd> start
> >
> >When testing launch time feature with igc driver, firstly, some code
> >change made in txonly.c:
> >pkt->ol_flags |= RTE_MBUF_F_TX_IEEE1588_TMST; (this flag should be
> >pkt->added to
> >forward PTP packet with hardware Tx timestamp)
> >
> ># ./build/app/dpdk-testpmd -a 0000:81:00.0 -c f -n 4 -- -i
> >--tx-offloads=0x200000
> >testpmd> set burst 1
> >testpmd> set fwd txonly
> >testpmd> set txtimes 1000000,0
> >testpmd> start
> >
> >On receiver side (with tcpdump):
> ># tcpdump -Q in -ttt -ni ens25f3 --time-stamp-precision=nano -j
> >adapter_unsynced -c 32
>
> Now dpdk-testpmd works well with this patch after I add the flag in txonly.c as
> you mentioned.
OK, good.
>
> It is worth noting that I also added `rte_eth_timesync_enable(pi);` in the
> function `tx_only_begin` in txonly.c to enable the PTP clock. Otherwise, all Tx
> packets scheduled are dropped.
Yes, got it.
>
> Following are the measurement results on the listener. I use the same
> configuration as you mentioned for dpdk-testpmd on the talker.
>
> ➜ ~ sudo tcpdump -Q in -ttt -ni enp1s0 --time-stamp-precision=nano -j
> adapter_unsynced -c 32
>
> tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
> listening on enp1s0, link-type EN10MB (Ethernet), snapshot length
> 262144 bytes
>
>
> 00:00:00.000000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000008 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> ....
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000008 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 00:00:00.001000000 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
> 32 packets captured
> 118 packets received by filter
> 0 packets dropped by kernel
>
> Above test is based on the patch v2 with Intel i210 NIC.
OK. I will review v2 patch.
Thanks,
Simei
>
> - Chuanyu
next prev parent reply other threads:[~2024-01-04 2:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 20:20 Chuanyu Xue
2023-12-20 6:29 ` Su, Simei
2023-12-22 3:03 ` Chuanyu Xue
2023-12-26 9:33 ` Su, Simei
2023-12-29 21:29 ` Chuanyu Xue
2024-01-03 2:26 ` Su, Simei
2024-01-03 21:52 ` Chuanyu Xue
2024-01-04 2:56 ` Su, Simei [this message]
2023-12-30 16:35 ` [PATCH v2] " Chuanyu Xue
2024-01-04 3:13 ` Su, Simei
2024-01-05 0:51 ` Zhang, Qi Z
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=SA1PR11MB6613E0A06CB069024AF11DB29C67A@SA1PR11MB6613.namprd11.prod.outlook.com \
--to=simei.su@intel.com \
--cc=beilei.xing@intel.com \
--cc=chuanyu.xue@uconn.edu \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@intel.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).