Wu, Jingjing ;
> dev@dpdk.org; Zhao1, Wei ; Guo, Jia
> ; Yigit, Ferruh
> Subject: Re: [dpdk-dev] CALL to eth PMD maintainers: complete closing of
> port
>
> 22/09/2020 05:04, Xu, Rosen:
> > Hi Thomas,
> >
> > Ipn3ke is based on ifpga_bus, and all ethdevs
Hi Thomas,
>From: dev On Behalf Of Thomas Monjalon
>Sent: Sunday, September 13, 2020 3:16 PM
>
>The patches for removing RTE_ETH_DEV_CLOSE_REMOVE are sent:
> https://urldefense.proofpoint.com/v2/url?u=https-
>3A__patches.dpdk.org_project_dpdk_list_-3Fseries-
>3D12173&d=DwICAg&c=nKjWec2b6R0m
22/09/2020 05:04, Xu, Rosen:
> Hi Thomas,
>
> Ipn3ke is based on ifpga_bus, and all ethdevs created from ipn3ke are
> representors.
> So it's no need to add RTE_ETH_DEV_CLOSE_REMOVE flags into ipn3ke driver.
I don't understand how it is related.
Do you mean it will work fine with the new close b
n Wang ; Guoyang Zhou
> ; Min Hu (Connor) ;
> Yisen Zhuang ; Alfredo Cardigliano
> ; Jakub Grajciar ; Viacheslav
> Ovsiienko ; Long Li ;
> Martin Spinler ; Heinrich Kuhn
> ; Harman Kalra ;
> Nithin Dabilpuram ; Kiran Kumar K
> ; Akhil Goyal ; Yigit,
> Ferruh ; Thomas Monjalon
On Monday, September 09/14/20, 2020 at 00:16:17 +0200, Thomas Monjalon wrote:
> The patches for removing RTE_ETH_DEV_CLOSE_REMOVE are sent:
> https://patches.dpdk.org/project/dpdk/list/?series=12173
>
> 11 drivers are not supporting the new behaviour correctly:
> bnx2x, cxgbe, dpaa, dp
The patches for removing RTE_ETH_DEV_CLOSE_REMOVE are sent:
https://patches.dpdk.org/project/dpdk/list/?series=12173
11 drivers are not supporting the new behaviour correctly:
bnx2x, cxgbe, dpaa, dpaa2, enetc, ionic,
ipn3ke, liquidio, nfp, pfe, qede
If you are the maintain
03/08/2020 20:50, Thomas Monjalon:
> 18/04/2019 12:59, Thomas Monjalon:
> > Hi all,
> >
> > Since DPDK 18.11, the behaviour of the close operation is changed
> > if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> > port is released (i.e. totally freed and data erased) on close.
> > This new b
18/04/2019 12:59, Thomas Monjalon:
> Hi all,
>
> Since DPDK 18.11, the behaviour of the close operation is changed
> if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> port is released (i.e. totally freed and data erased) on close.
> This new behaviour is enabled per driver for a migration pe
30/04/2019 14:45, Nithin Dabilpuram:
> On Mon, Apr 29, 2019 at 10:30:00PM +0200, Thomas Monjalon wrote:
> > 29/04/2019 18:51, Ferruh Yigit:
> > > I would like to detail a little more what needs to be done, mainly for
> > > the sake
> > > of the discussion, please comment if something missing/wrong
On Mon, Apr 29, 2019 at 10:30:00PM +0200, Thomas Monjalon wrote:
> 29/04/2019 18:51, Ferruh Yigit:
> > On 4/18/2019 11:59 AM, Thomas Monjalon wrote:
> > > Hi all,
> > >
> > > Since DPDK 18.11, the behaviour of the close operation is changed
> > > if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the drive
29/04/2019 18:51, Ferruh Yigit:
> On 4/18/2019 11:59 AM, Thomas Monjalon wrote:
> > Hi all,
> >
> > Since DPDK 18.11, the behaviour of the close operation is changed
> > if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> > port is released (i.e. totally freed and data erased) on close.
> > Th
On 4/18/2019 11:59 AM, Thomas Monjalon wrote:
> Hi all,
>
> Since DPDK 18.11, the behaviour of the close operation is changed
> if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> port is released (i.e. totally freed and data erased) on close.
> This new behaviour is enabled per driver for a m
On Sun, 28 Apr 2019 06:57:59 +
Matan Azrad wrote:
> Hi Thomas
>
> vdev_netvsc has no close API - should I change something there?
>
> > From: Thomas Monjalon
> > Hi all,
> >
> > Since DPDK 18.11, the behaviour of the close operation is changed if
> > RTE_ETH_DEV_CLOSE_REMOVE is enabled in
Hi Thomas
vdev_netvsc has no close API - should I change something there?
> From: Thomas Monjalon
> Hi all,
>
> Since DPDK 18.11, the behaviour of the close operation is changed if
> RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> port is released (i.e. totally freed and data erased) on
Hi all,
Since DPDK 18.11, the behaviour of the close operation is changed
if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
port is released (i.e. totally freed and data erased) on close.
This new behaviour is enabled per driver for a migration period.
Looking at the code, you can see these c
15 matches
Mail list logo
