From: Bruce Richardson <bruce.richardson@intel.com>
To: Raz Amir <razamir22@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pci: save list of detached devices, and re-probe during driver unload
Date: Wed, 4 Mar 2015 10:13:01 +0000 [thread overview]
Message-ID: <20150304101301.GA1468@bricha3-MOBL3> (raw)
In-Reply-To: <053901d0565a$ac8c36e0$05a4a4a0$@gmail.com>
On Wed, Mar 04, 2015 at 11:07:41AM +0200, Raz Amir wrote:
> Thank you.
>
> See answers inline (mostly ack, but not only), and I will send the updated
> patch soon.
>
>
>
> > -----Original Message-----
>
> > From: Bruce Richardson [mailto:bruce.richardson@intel.com]
>
> > Sent: 03 March 2015 15:33
>
> > To: Raz Amir
>
> > Cc: dev@dpdk.org
>
> > Subject: Re: [dpdk-dev] [PATCH] pci: save list of detached devices, and
> re-
>
> > probe during driver unload
>
> >
>
> > On Thu, Feb 26, 2015 at 06:33:20AM +0000, Raz Amir wrote:
>
> > > Added code that saves the pointers to the detached devices, during
>
> > > driver loading, and during driver unloading, go over the list, and
>
> > > re-attach them by calling device_probe_and_attach on each device.
>
> > >
>
> > > Signed-off-by: Raz Amir < <mailto:razamir22@gmail.com>
> razamir22@gmail.com>
>
> >
>
> > Couple of minor comments below. Otherwise all looks good to me.
>
> >
>
> > Acked-by: Bruce Richardson < <mailto:bruce.richardson@intel.com>
> bruce.richardson@intel.com>
>
> > > ---
>
> > > lib/librte_eal/bsdapp/nic_uio/nic_uio.c | 26
>
> > > +++++++++++++++++++++++++-
>
> > > 1 file changed, 25 insertions(+), 1 deletion(-)
>
> > >
>
> > > diff --git a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
>
> > > b/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
>
> > > index 5ae8560..7d702a5 100644
>
> > > --- a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
>
> > > +++ b/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
>
> > > @@ -55,6 +55,9 @@ __FBSDID("$FreeBSD$");
>
> > >
>
> > > #define MAX_BARS (PCIR_MAX_BAR_0 + 1)
>
> > >
>
> > > +#define MAX_DETACHED_DEVICES 128
>
> > > +static device_t detached_devices[MAX_DETACHED_DEVICES] = {}; static
>
> > > +int last_detached = 0;
>
> > Maybe num_detached/nb_detached or even just "detached" instead of
>
> > "last_detached".
>
> Ack.
>
>
>
> >
>
> > >
>
> > > struct nic_uio_softc {
>
> > > device_t dev_t;
>
> > > @@ -291,14 +294,35 @@ nic_uio_load(void)
>
> > > if (dev != NULL)
>
> >
>
> > We are getting into some serious levels of indentation below, so maybe
> flip
>
> > this condition around and put in a "continue" instead, so that we can
> dedent
>
> > everything below that follows it.
>
> >
>
> Ack.
>
>
>
> > > for (i = 0; i < NUM_DEVICES;
> i++)
>
> > > if
> (pci_get_vendor(dev) == devices[i].vend
>
> > &&
>
> > > -
> pci_get_device(dev) ==
>
> > devices[i].dev)
>
> > > +
> pci_get_device(dev) ==
>
> > devices[i].dev) {
>
> > > +
> if (last_detached+1 <
>
> > MAX_DETACHED_DEVICES) {
>
> > I don't think you need the +1 here.
>
> It is needed, otherwise the last object will be added at
> MAX_DETACHED_DEVICES position while the last position is
> MAX_DETACHED_DEVICES-1.
Yes, the last position is MAX_DETACHED_DEVICES-1, but you do the addition
of the element to the array using "detached_devices[last_detached++]", i.e. a
post-increment, so when last_detached == (MAX_DETACHED_DEVICES-1), you still
can fill in an entry. Next time around, when last_detached == MAX_DETACHED_DEVICES
it's no longer safe to add, and the condition "last_detached < MAX_DETACHED_DEVICES)
will now fail. No +1 or -1 necessary to prevent this.
/Bruce
next prev parent reply other threads:[~2015-03-04 10:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 6:33 Raz Amir
2015-03-01 13:48 ` Neil Horman
2015-03-01 14:21 ` Raz Amir
2015-03-01 17:16 ` Neil Horman
2015-03-02 8:18 ` Raz Amir
2015-03-02 11:36 ` Neil Horman
2015-03-02 11:58 ` Raz Amir
2015-03-02 13:29 ` Thomas Monjalon
2015-03-03 11:30 ` Raz Amir
2015-03-03 11:45 ` Bruce Richardson
2015-03-03 12:56 ` Raz Amir
2015-03-03 13:32 ` Bruce Richardson
2015-03-04 9:07 ` Raz Amir
2015-03-04 10:13 ` Bruce Richardson [this message]
2015-03-04 10:28 ` Raz Amir
2015-03-04 11:15 ` [dpdk-dev] [PATCH v3] " Raz Amir
2015-03-09 8:07 ` Raz Amir
2015-03-09 10:27 ` Bruce Richardson
2015-03-10 8:15 ` Raz Amir
2015-03-04 11:47 ` [dpdk-dev] [PATCH v2] " Raz Amir
2015-03-05 14:59 ` [dpdk-dev] [PATCH v4] " Raz Amir
2015-03-05 16:24 ` Raz Amir
2015-03-11 10:26 ` Bruce Richardson
2015-03-12 12:24 ` Raz Amir
2015-03-16 16:29 ` Thomas Monjalon
2015-07-08 22:51 ` 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=20150304101301.GA1468@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=razamir22@gmail.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).