DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/nfp: add CPP bridge as service
Date: Sun, 13 Jan 2019 22:41:36 +0100	[thread overview]
Message-ID: <1753333.lH3haCoHOP@xps> (raw)
In-Reply-To: <1051920a-7b6b-f68e-7556-be74c160a477@intel.com>

11/01/2019 17:42, Ferruh Yigit:
> On 1/11/2019 1:25 PM, Alejandro Lucero wrote:
> > The Netronome's Network Flow Processor chip is highly programmable
> > with the goal of processing packets at high speed. Processing units
> > and other chip components are available from the host through the
> > PCIe CPP(Command Push Pull bus) interface. The NFP PF PMD configures
> > a CPP handler for setting up and working with vNICs, perform actions
> > like link up or down, or accessing extended stats from the MAC component.
> > 
> > There exist NFP host tools which access the NFP components for
> > programming and debugging but they require the CPP interface. When the
> > PMD is bound to the PF, the DPDK app owns the CPP interface, so these
> > host tools can not access the NFP through other means like NFP kernel
> > drivers.
> > 
> > This patch adds a CPP bridge using the rte_service API which can be
> > enabled by a DPDK app. Interestingly, DPDK clients like OVS will not
> > enable specific service cores, but this can be performed with a
> > secondary process specifically enabling this CPP bridge service and
> > therefore giving access to the NFP to those host tools.
> > 
> > v2:
> >  - Avoid printfs for debugging
> >  - fix compilation problems for powerpc
> > 
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> 
> Applied to dpdk-next-net/master, thanks.

It does not compile with 32-bit toolchain.

Please check the occurences of %lu, thanks.

  reply	other threads:[~2019-01-13 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 13:25 Alejandro Lucero
2019-01-11 16:42 ` Ferruh Yigit
2019-01-13 21:41   ` Thomas Monjalon [this message]
2019-01-14 10:40     ` Ferruh Yigit
2019-01-14 18:00       ` Alejandro Lucero
2019-01-14 18:22         ` Ferruh Yigit
2019-01-14 18:29           ` Alejandro Lucero
2019-01-14 18:54             ` Thomas Monjalon
2019-01-14 19:26               ` Alejandro Lucero
  -- strict thread matches above, loose matches on Subject: below --
2019-01-03  8:56 Alejandro Lucero
2019-01-09 10:54 ` Ferruh Yigit
2019-01-09 14:20   ` Alejandro Lucero
2019-01-09 16:15     ` Ferruh Yigit
2019-01-10 11:55       ` Alejandro Lucero
2019-01-11 11:48         ` Ferruh Yigit
2019-01-11 12:15           ` Alejandro Lucero
2019-01-11 12:35             ` Ferruh Yigit

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=1753333.lH3haCoHOP@xps \
    --to=thomas@monjalon.net \
    --cc=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).