> -----Original Message-----
> From: Thomas Monjalon <tho...@monjalon.net>
> Sent: Tuesday, August 6, 2019 4:08 PM
> To: Phil Yang (Arm Technology China) <phil.y...@arm.com>;
> jgraj...@cisco.com
> Cc: dev@dpdk.org; anatoly.bura...@intel.com; ferruh.yi...@intel.com;
> Gavin Hu (Arm Technology China) <gavin...@arm.com>; Honnappa
> Nagarahalli <honnappa.nagaraha...@arm.com>; nd <n...@arm.com>
> Subject: Re: [dpdk-dev] [PATCH] net/memif: fix multi-process device probe
> error
>
> 02/08/2019 23:01, Thomas Monjalon:
> > 01/08/2019 12:35, Phil Yang:
> > > Fixes: c41a04958b ("net/memif: support multi-process")
> > >
> > > Signed-off-by: Phil Yang <phil.y...@arm.com>
> > > Reviewed-by: Gavin Hu <gavin...@arm.com>
> > > ---
> > > --- a/drivers/net/memif/rte_eth_memif.c
> > > +++ b/drivers/net/memif/rte_eth_memif.c
> > > @@ -1265,7 +1265,7 @@ rte_pmd_memif_probe(struct
> rte_vdev_device *vdev)
> > > eth_dev->dev_ops = &ops;
> > > eth_dev->device = &vdev->device;
> > > eth_dev->rx_pkt_burst = eth_memif_rx;
> > > - eth_dev->tx_pkt_burst = eth_memif_rx;
> > > + eth_dev->tx_pkt_burst = eth_memif_tx;
> >
Hi Thomas,
Sorry for the later response.
> > It is not a probe error, but malfunctioning device, right?
Yes, agree.
> > What is the current behaviour? You could better explain
> > the symptom in the commit log, and the root cause (typo).
Since testpmd has issues working as a secondary process, so I cannot get the
typo for this issue.
But in logically, the memif PMD should use eth_memif_tx in the egress path.
I will update the commit log in v2.
>
> Nobody is replying or sending a v2?
> Jakub?
>
Thanks,
Phil
