DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] nfp: avoiding concurrency when hardware reconfig
Date: Tue, 3 May 2016 12:20:13 +0100	[thread overview]
Message-ID: <20160503112012.GD20328@bricha3-MOBL3> (raw)
In-Reply-To: <CAD+H992+EGdXaPt2HUteC0s_JyjLEXLpDGS9LLsEO2zG03mWNQ@mail.gmail.com>

On Tue, May 03, 2016 at 12:14:26PM +0100, Alejandro Lucero wrote:
> Hi Bruce,
> 
> Sorry about this. I sent a v2 for this patch but not in the same thread:
> 
> http://www.dpdk.org/ml/archives/dev/2016-April/037996.html
> 

Ok, I see it in patchwork now, thanks.

When sending a v2, please keep the mails threaded, and please also update the
original patch submission in patchwork to "superceded" so that it drops off the
list of patches for consideration in DPDK. [That way at least if you forget one,
the other will help hint to committers that they are not looking at the latest
version. :-)]

/Bruce

> On Tue, May 3, 2016 at 12:01 PM, Bruce Richardson <
> bruce.richardson@intel.com> wrote:
> 
> > On Tue, Apr 26, 2016 at 01:14:15PM +0100, Alejandro Lucero wrote:
> > > Some apps calling some functions from different threads at the
> > > same time could lead to reconfig problems. Reconfig mechanism is
> > > based on a hardware queue where incrementing a counter signals the
> > > firmware to do the reconfig. If there are two increments before the
> > > first one has been processed the firmware will stop and a device
> > > reset is necessary.
> > >
> > > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> > > ---
> > >  drivers/net/nfp/nfp_net.c     | 8 ++++++++
> > >  drivers/net/nfp/nfp_net_pmd.h | 1 +
> > >  2 files changed, 9 insertions(+)
> > >
> > > diff --git a/drivers/net/nfp/nfp_net.c b/drivers/net/nfp/nfp_net.c
> > > index bc0a3d8..ba0ee04 100644
> > > --- a/drivers/net/nfp/nfp_net.c
> > > +++ b/drivers/net/nfp/nfp_net.c
> > > @@ -58,6 +58,7 @@
> > >  #include "nfp_net_pmd.h"
> > >  #include "nfp_net_logs.h"
> > >  #include "nfp_net_ctrl.h"
> > > +#include <rte_spinlock.h>
> >
> > Hi Alejandro,
> >
> > I think this header addition is in the wrong place in the code. When I
> > apply
> > this patch to next-net and try a recompile I get the error:
> >
> >   CC nfp_net.o
> >   In file included from
> > /home/bruce/next-net/dpdk-next-net/drivers/net/nfp/nfp_net.c:58:0:
> >   /home/bruce/next-net/dpdk-next-net/drivers/net/nfp/nfp_net_pmd.h:409:2:
> > error: unknown type name ‘rte_spinlock_t’
> >     rte_spinlock_t reconfig_lock;
> >     ^
> >
> > You either need to put the spinlock include before the nfp_net_pmd.h
> > include
> > or, perhaps better, put the spinlock include inside the nfp_net_pmd header
> > file
> > since that is where the spinlock variable is being defined.
> >
> > /Bruce
> >
> >

      reply	other threads:[~2016-05-03 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 12:14 Alejandro Lucero
2016-05-03 11:01 ` Bruce Richardson
2016-05-03 11:14   ` Alejandro Lucero
2016-05-03 11:20     ` Bruce Richardson [this message]

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=20160503112012.GD20328@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    /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).