> -Original Message-
> From: Wu, WenxuanX
> Sent: 2022年3月9日 11:07
> To: Yigit, Ferruh ; Li, Xiaoyun
> ;
> dev@dpdk.org
> Cc: sta...@dpdk.org
> Subject: RE: [PATCH v2 2/2] app/testpmd:fix testpmd quit failure
>
>
>
> > -Original Message-
> -Original Message-
> From: Yigit, Ferruh
> Sent: 2022年3月5日 0:16
> To: Wu, WenxuanX ; Li, Xiaoyun
> ; dev@dpdk.org
> Cc: sta...@dpdk.org
> Subject: Re: [PATCH v2 2/2] app/testpmd:fix testpmd quit failure
>
> On 3/3/2022 1:22 PM, Wu, WenxuanX wrote:
>
On 3/3/2022 1:22 PM, Wu, WenxuanX wrote:
moved down, please don't top post
-Original Message-
From: Wu, WenxuanX
Sent: 2022年2月23日 19:33
To: Li, Xiaoyun ; Yigit, Ferruh
; dev@dpdk.org
Cc: Wu, WenxuanX ; sta...@dpdk.org
Subject: [PATCH v2 2/2] app/testpmd:fix testpmd quit failure
From:
I found this meaning in DPDK testplan.
Note that currently hot-plugging of representor ports is not supported so all
the required representors must be specified on the creation of the PF or the
trusted VF.
When testpmd is started with pf and vf representors, the order of representor
is determin
On 2/23/2022 11:32 AM, wenxuanx...@intel.com wrote:
From: wenxuan wu
When testpmd start ed with 1 pf and 2 vfs, testpmd quited while vfs
were still alive would result in failure. Root cause is that pf had
been released already but vfs were still accessing by func
rte_eth_dev_info_get, which wou
5 matches
Mail list logo
