From: Wisam Monther <wisamm@mellanox.com>
To: Lijun Ou <oulijun@huawei.com>,
"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
"beilei.xing@intel.com" <beilei.xing@intel.com>,
"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix missing set for current forward engine
Date: Thu, 2 Jul 2020 08:11:48 +0000 [thread overview]
Message-ID: <AM0PR05MB661064BB6E0AE9C170C516EEA96D0@AM0PR05MB6610.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1593589406-12868-1-git-send-email-oulijun@huawei.com>
Hi,
>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Lijun Ou
>Sent: Wednesday, July 1, 2020 10:43 AM
>To: wenzhuo.lu@intel.com; beilei.xing@intel.com;
>bernard.iremonger@intel.com; ferruh.yigit@intel.com
>Cc: dev@dpdk.org; linuxarm@huawei.com
>Subject: [dpdk-dev] [PATCH v2] app/testpmd: fix missing set for current
>forward engine
>
>When set the forwarding mode of the pkt, it needs to update the fwd_eng that
>it is the member of cur_fwd_config. Otherwise, an error will occur when
>executing the set command and show confg fwd.
>the flows as follows:
> 1. ./tespmd -w xxx -l xx -n 4 -- i
> 2. set fwd mac
> testpmd> set fwd mac
> Set mac packet forwarding mode
>
> 3. show config fwd
> testpmd> show config fwd
> io packet forwarding - ports=1 - cores=1 - streams=8 -...
> Logical Core 1 (socket 0) forwards packets on 8 streams:
>
>When run the 1 ~ 3 step, it should show the packet forwarding is mac.
>
>Fixes: af75078fece3 ("first public release")
>Cc: wenzhuo.lu@intel.com
>Cc: beilei.xing@intel.com
>Cc: bernard.iremonger@intel.com
>Cc: stable@dpdk.org
>
>Signed-off-by: Lijun Ou <oulijun@huawei.com>
Acked-by: Wisam Jaddo <wisamm@mellanox.com>
next prev parent reply other threads:[~2020-07-02 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:43 Lijun Ou
2020-07-02 8:11 ` Wisam Monther [this message]
2020-07-02 15:03 ` Phil Yang
2020-07-03 1:31 ` Phil Yang
2020-07-15 10:35 ` Phil Yang
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=AM0PR05MB661064BB6E0AE9C170C516EEA96D0@AM0PR05MB6610.eurprd05.prod.outlook.com \
--to=wisamm@mellanox.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linuxarm@huawei.com \
--cc=oulijun@huawei.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).