From: Thomas Monjalon <thomas@monjalon.net>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
dev@dpdk.org, Zhiyong Yang <zhiyong.yang@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix failsafe PMD failure on exit
Date: Sun, 27 May 2018 14:37:28 +0200 [thread overview]
Message-ID: <6066559.Wi7eJV5HDK@xps> (raw)
In-Reply-To: <20180527040630.x3wrjsblyqbxk3bz@yuanhanliu-NB0.tencent.com>
27/05/2018 06:06, Yuanhan Liu:
> On Tue, May 22, 2018 at 07:35:08PM +0100, Ferruh Yigit wrote:
> > + /*
> > + * This is a workaround to fix a virtio-user issue that
> > + * requires to call clean-up routine to remove existing
> > + * socket.
>
> I came across this patch while I was cherry-picking patches to 17.11.4
> release. And this patch seems wrong to me.
Yes it is far from perfect.
> Any particular reason why the socket removal can not be done in virtio-user
> pmd, say at its close method?
The socket is removed in the remove function of the driver.
The right fix is to call the remove functions of all driver from
the EAL cleanup function.
We have decided of this last minute workaround for testpmd
because we need it for testing convenience, but do not want to
take any risk with a proper fix as it is really late for that.
> > + * This workaround valid only for testpmd, needs a fix
> > + * valid for all applications.
> > + * TODO: Implement proper resource cleanup
> > + */
> > + device = rte_eth_devices[pt_id].device;
> > + if (device && !strcmp(device->driver->name, "net_virtio_user"))
> > detach_port(pt_id);
> > }
> > }
>
next prev parent reply other threads:[~2018-05-27 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 18:35 Ferruh Yigit
2018-05-22 19:47 ` Thomas Monjalon
2018-05-22 20:49 ` Ferruh Yigit
2018-05-22 20:50 ` Ferruh Yigit
2018-05-27 4:06 ` Yuanhan Liu
2018-05-27 12:37 ` Thomas Monjalon [this message]
2018-06-02 5:01 ` Yuanhan Liu
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=6066559.Wi7eJV5HDK@xps \
--to=thomas@monjalon.net \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=wenzhuo.lu@intel.com \
--cc=yliu@fridaylinux.org \
--cc=zhiyong.yang@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).