From: "Xu, Ke1" <ke1.xu@intel.com>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>,
"dts@dpdk.org" <dts@dpdk.org>,
"dts-test-report@dpdk.org" <dts-test-report@dpdk.org>
Subject: RE: dpdk 22.11 release issues
Date: Tue, 6 Dec 2022 08:24:09 +0000 [thread overview]
Message-ID: <PH7PR11MB6056ABFF968D4046B405EDFED31B9@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CA++2-x6nfG+mPUsiqX5s-NN7mDYs4kRZEuvO8o7cJQP7iZUd3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Hi,
You may try:
testpmd> port stop all
or:
testpmd> port stop <port_id>
to stop a port, while ‘stop’ and ‘start’ here is actually stop or start fwd engine.
Regards,
XU KE.
From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Sent: Thursday, December 1, 2022 8:04 PM
To: dts@dpdk.org; dts-test-report@dpdk.org
Subject: dpdk 22.11 release issues
I have faced the following issues in new dpdk 22.11 released version:
testpmd> port config 0 speed 100 duplex half
Please stop port 0 first
dpdk 22.11 error: please stop port 0 first dpdk even though it's already stopped!
same for :
testpmd> port config 0 tx_offload vlan_insert on
Error: Can't config offload when Port 0 is not stopped
testpmd> stop
Packet forwarding not started
testpmd> port config 0 tx_offload vlan_insert on
Error: Can't config offload when Port 0 is not stopped
regards,
--
Engr. Khadem Ullah
Research Assistant at National Center Of Big Data and Cloud Computing,
University Of Engineering and Technology Peshawar (NCBC-UETP) Pakistan
[-- Attachment #2: Type: text/html, Size: 4998 bytes --]
next prev parent reply other threads:[~2022-12-06 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:03 Khadem Ullah
2022-12-06 8:24 ` Xu, Ke1 [this message]
2022-12-07 5:43 ` Khadem Ullah
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=PH7PR11MB6056ABFF968D4046B405EDFED31B9@PH7PR11MB6056.namprd11.prod.outlook.com \
--to=ke1.xu@intel.com \
--cc=14pwcse1224@uetpeshawar.edu.pk \
--cc=dts-test-report@dpdk.org \
--cc=dts@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).