From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Yao, Lei A" <lei.a.yao@intel.com>,
"Yang, Zhiyong" <zhiyong.yang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Harry Van Haaren <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix pmd_test_exit function for vdevs
Date: Fri, 18 May 2018 17:29:10 +0100 [thread overview]
Message-ID: <f16bb33b-a3bc-c7ae-8b4b-ff2760e130fc@intel.com> (raw)
In-Reply-To: <VI1PR0501MB26080DBFA8CACD88E5A9F633D2900@VI1PR0501MB2608.eurprd05.prod.outlook.com>
On 5/18/2018 4:55 PM, Matan Azrad wrote:
> Hi all
>
> While this patch also applied I don't understand it.
> Is it mandatory for each PMD to free all its resources in dev_close()?
> Or it should be done by the rte_device remove function?
>
> If the resource cleanup should be done by the remove function I think it
> should be called for all the devices (pci, vdev, etc).
>
> Is there an exit function for EAL to clean rte_eal_init()? If no, looks like we need it...
Hi Matan,
I believe there is a gap in resource cleanup.
dev_close() it not for resource cleanup, it should be in PMD remove() functions,
and PMDs have it. The problem is remove path is not called in application exit.
As far as I know there is no simple API to clean the resources, having it may
help application to do the cleanup.
I have seen the rte_eal_cleanup() API by Harry, that can be extended to cover
PMD resource cleanup if there is enough motivation for it.
>
> From: Ferruh Yigit
>>
>> On 5/18/2018 11:18 AM, Iremonger, Bernard wrote:
>>> Hi Ferruh, Zhiyong,
>>>
>>> <snip>
>>>
>>>>> Subject: [PATCH v2] app/testpmd: fix pmd_test_exit function for
>>>>> vdevs
>>>>>
>>>>> For vdev, just calling rte_eth_dev_close() isn't enough to free all
>>>>> the resources allocated during device probe, e.g. for virtio-user,
>>>>> virtio_user_pmd_remove(), i.e. the remove() method of a vdev driver,
>>>>> needs to be called to unlink the socket file created during device
>>>>> probe. So this patch calls the rte_eth_dev_detach() for vdev when
>>>>> quitting testpmd.
>>>>>
>>>>> Cc: maxime.coquelin@redhat.com
>>>>> Cc: ferruh.yigit@intel.com
>>>>> Cc: tiwei.bie@intel.com
>>>>> Cc: lei.a.yao@intel.com
>>>>> Cc: bernard.iremonger@intel.com
>>>>> Cc: stable@dpdk.org
>>>>>
>>>>> Fixes: af75078fece3 ("first public release")
>>>>> Fixes: bd8f50a45d0f ("net/virtio-user: support server mode")
>>>>>
>>>>> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
>>>> Tested-by: Lei Yao<lei.a.yao@intel.com> This patch pass the test for
>>>> virtio-user server mode. The socket file can be deleted after quit
>>>> testpmd.
>>>
>>> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
>>
>> Applied to dpdk-next-net/master, thanks.
>>
>>
>>> Check-git-log is showing some errors:
>>>
>>> ./devtools/check-git-log.sh -1
>>> Wrong headline format:
>>> app/testpmd: fix pmd_test_exit function for vdevs Wrong tag:
>>> Tested-by: Lei Yao<lei.a.yao@intel.com>
>>
>> fixed while applying.
next prev parent reply other threads:[~2018-05-18 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 9:59 zhiyong.yang
2018-05-18 4:52 ` Yao, Lei A
2018-05-18 10:18 ` Iremonger, Bernard
2018-05-18 10:21 ` Ferruh Yigit
2018-05-18 10:48 ` Ferruh Yigit
2018-05-18 15:55 ` Matan Azrad
2018-05-18 16:29 ` Ferruh Yigit [this message]
2018-05-19 14:19 ` Thomas Monjalon
2018-05-21 10:54 ` Thomas Monjalon
2018-05-21 16:32 ` Ferruh Yigit
2018-05-21 16:38 ` Thomas Monjalon
2018-05-22 13:12 ` Thomas Monjalon
2018-05-22 18:38 ` Ferruh Yigit
2018-05-22 19:48 ` Thomas Monjalon
2018-05-23 1:52 ` Yang, Zhiyong
2018-05-23 11:37 ` Yang, Zhiyong
2018-05-23 11:58 ` Thomas Monjalon
2018-05-21 16:37 ` Ferruh Yigit
2018-05-21 16:40 ` Thomas Monjalon
2018-05-21 16:44 ` Ferruh Yigit
2018-05-21 19:12 ` Thomas Monjalon
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=f16bb33b-a3bc-c7ae-8b4b-ff2760e130fc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=lei.a.yao@intel.com \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.com \
--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).