From: David Marchand <david.marchand@redhat.com>
To: Muhammad Bilal <m.bilal@emumba.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Vipin Varghese" <vipin.varghese@intel.com>,
"Jakub Grajciar" <jgrajcia@cisco.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
dev <dev@dpdk.org>, "dpdk stable" <stable@dpdk.org>,
"Gaëtan Rivet" <grive@u256.net>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] EAL: Called remove() of drivers for vdev and pci buses
Date: Tue, 20 Oct 2020 15:43:16 +0200 [thread overview]
Message-ID: <CAJFAV8z3enGMcZPNHT972y_y2jVkYtXyb=JE5ekh1ByNVD1RAw@mail.gmail.com> (raw)
In-Reply-To: <20200912195337.734ez2cumf6x7hxp@u256.net>
Hello,
On Sat, Sep 12, 2020 at 9:53 PM Gaëtan Rivet <grive@u256.net> wrote:
>
> On 08/07/20 17:03 +0500, Muhammad Bilal wrote:
> > while using memif with app, the resources are not cleaned on exit,
> > So an error occurred on running it second time. The cause of this problem
> > is that remove() of memif driver is not called by rte_eal_cleanup() which
> > is counterpart of probe() called from rte_eal_init(). This is a case for
> > all other divers e.g pci, so to solve this problem I have added the
> > functionality of calling remove() function of all the driver attached to
> > devices on vdev and pci buses.
> >
>
> Hi Muhammad,
>
> review inline.
There were comments from Gaetan, waiting for a v2.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-10-20 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 12:03 [dpdk-dev] " Muhammad Bilal
2020-07-08 14:11 ` Muhammad Bilal
2020-09-12 19:53 ` Gaëtan Rivet
2020-10-20 13:43 ` David Marchand [this message]
2020-10-25 21:28 ` [dpdk-dev] [dpdk-stable] " Muhammad Bilal
2021-03-25 15:27 ` David Marchand
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='CAJFAV8z3enGMcZPNHT972y_y2jVkYtXyb=JE5ekh1ByNVD1RAw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=grive@u256.net \
--cc=jerinj@marvell.com \
--cc=jgrajcia@cisco.com \
--cc=m.bilal@emumba.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@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).