DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Rastislav Cernay <cernay@netcope.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/nfb: new netcope driver
Date: Tue, 05 Mar 2019 22:41:14 +0000	[thread overview]
Message-ID: <130a4780434ea30138a7c98f5689da143c73a8a1.camel@debian.org> (raw)
In-Reply-To: <1551451054-111249-1-git-send-email-cernay@netcope.com>

On Fri, 2019-03-01 at 15:37 +0100, Rastislav Cernay wrote:
> From: Rastislav Cernay <cernay@netcope.com>
> 
> Added new net driver for Netcope nfb cards
> 
> Signed-off-by: Rastislav Cernay <cernay@netcope.com>
> ---
> v2: remove unnecessary cast
>     remove unnecessary zeroing
>     move declaration to not mix with code
>     restore skeleton example
> v3: add release notes
>     add doc to doc index
>     add architecture limits to doc
>     edit features list
>     add .map file
>     change link to dependecies to official vendor site
>     move declarations out of code
>     remove false comments (rte_errno is set)
>     comments to c89 style
>     remove log from main rx loop
>     remove redundant code
>  MAINTAINERS                             |   7 +
>  config/common_base                      |   4 +
>  devtools/test-build.sh                  |   1 +
>  doc/guides/nics/features/nfb.ini        |  18 +
>  doc/guides/nics/index.rst               |   1 +
>  doc/guides/nics/nfb.rst                 | 143 ++++++++
>  doc/guides/rel_notes/release_19_02.rst  |   5 +
>  drivers/net/Makefile                    |   1 +
>  drivers/net/meson.build                 |   1 +
>  drivers/net/nfb/Makefile                |  41 +++
>  drivers/net/nfb/meson.build             |   9 +
>  drivers/net/nfb/nfb.h                   |  50 +++
>  drivers/net/nfb/nfb_ethdev.c            | 589
> ++++++++++++++++++++++++++++++++
>  drivers/net/nfb/nfb_rx.c                | 127 +++++++
>  drivers/net/nfb/nfb_rx.h                | 213 ++++++++++++
>  drivers/net/nfb/nfb_rxmode.c            | 100 ++++++
>  drivers/net/nfb/nfb_rxmode.h            |  78 +++++
>  drivers/net/nfb/nfb_stats.c             |  78 +++++
>  drivers/net/nfb/nfb_stats.h             |  48 +++
>  drivers/net/nfb/nfb_tx.c                | 113 ++++++
>  drivers/net/nfb/nfb_tx.h                | 204 +++++++++++
>  drivers/net/nfb/rte_nfb_pmd_version.map |   4 +
>  mk/rte.app.mk                           |   1 +
>  23 files changed, 1836 insertions(+)
>  create mode 100644 doc/guides/nics/features/nfb.ini
>  create mode 100644 doc/guides/nics/nfb.rst
>  create mode 100644 drivers/net/nfb/Makefile
>  create mode 100644 drivers/net/nfb/meson.build
>  create mode 100644 drivers/net/nfb/nfb.h
>  create mode 100644 drivers/net/nfb/nfb_ethdev.c
>  create mode 100644 drivers/net/nfb/nfb_rx.c
>  create mode 100644 drivers/net/nfb/nfb_rx.h
>  create mode 100644 drivers/net/nfb/nfb_rxmode.c
>  create mode 100644 drivers/net/nfb/nfb_rxmode.h
>  create mode 100644 drivers/net/nfb/nfb_stats.c
>  create mode 100644 drivers/net/nfb/nfb_stats.h
>  create mode 100644 drivers/net/nfb/nfb_tx.c
>  create mode 100644 drivers/net/nfb/nfb_tx.h
>  create mode 100644 drivers/net/nfb/rte_nfb_pmd_version.map
> 

<...>

> diff --git a/drivers/net/nfb/meson.build
> b/drivers/net/nfb/meson.build
> new file mode 100644
> index 0000000..d7dccba
> --- /dev/null
> +++ b/drivers/net/nfb/meson.build
> @@ -0,0 +1,9 @@
> +# SPDX-License-Identifier: BSD-3-Clause
> +# Copyright(c) 2018 Cesnet
> +# Copyright(c) 2018 Netcope Technologies, a.s. <info@netcope.com>
> +# All rights reserved.
> +
> +dep = cc.find_library('nfb', required: true)

This unconditionally breaks the build, please look at how
drivers/net/pcap/meson.build checks for dependencies for an example (I
assume libnfd does not provide a pkg-config file?)

> +build = dep.found()
> +ext_deps += dep
> +sources = files('nfb_rx.c', 'nfb_tx.c', 'nfb_stats.c',
> 'nfb_ethdev.c', 'nfb_rxmode.c')

<...>

> diff --git a/drivers/net/nfb/rte_nfb_pmd_version.map
> b/drivers/net/nfb/rte_nfb_pmd_version.map
> new file mode 100644
> index 0000000..97fd251
> --- /dev/null
> +++ b/drivers/net/nfb/rte_nfb_pmd_version.map
> @@ -0,0 +1,4 @@
> +DPDK_19.02 {
> +
> +        local: *;
> +};

These are all new symbols so they should be marked as experimental,
please see doc/guides/contributing/versioning.rst

> diff --git a/mk/rte.app.mk b/mk/rte.app.mk
> index 8a4f0f4..32e88b5 100644
> --- a/mk/rte.app.mk
> +++ b/mk/rte.app.mk
> @@ -196,6 +196,7 @@ _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_SOFTNIC)      +=
> -lrte_pmd_softnic
>  endif
>  _LDLIBS-$(CONFIG_RTE_LIBRTE_SFC_EFX_PMD)    += -lrte_pmd_sfc_efx
>  _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_SZEDATA2)   += -lrte_pmd_szedata2
> -lsze2
> +_LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_NFB)        += -lrte_pmd_nfb -lnfb
> -lfdt

Why is -lfdt added? I don't see any symbols from libfdt used in the
rest of the patch?

>  _LDLIBS-$(CONFIG_RTE_LIBRTE_PMD_TAP)        += -lrte_pmd_tap
>  _LDLIBS-$(CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD) +=
> -lrte_pmd_thunderx_nicvf
>  _LDLIBS-$(CONFIG_RTE_LIBRTE_VDEV_NETVSC_PMD) +=
> -lrte_pmd_vdev_netvsc

-- 
Kind regards,
Luca Boccassi

  parent reply	other threads:[~2019-03-05 22:41 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 12:57 [dpdk-dev] [PATCH] net/nfb: new Netcope driver Rastislav Cernay
2019-02-26 12:57 ` [dpdk-dev] [PATCH] net/nfb: new netcope driver Rastislav Cernay
2019-02-26 14:20   ` Rami Rosen
2019-02-26 16:33     ` Rastislav Černay
2019-02-26 15:46   ` Stephen Hemminger
2019-02-27 11:43   ` [dpdk-dev] [PATCH v2] net/nfb: new Netcope driver Rastislav Cernay
2019-02-27 15:28     ` Ferruh Yigit
2019-03-01 14:37   ` [dpdk-dev] [PATCH v3] net/nfb: new netcope driver Rastislav Cernay
2019-03-01 18:47     ` Stephen Hemminger
2019-03-04 14:07       ` Rastislav Černay
2019-03-01 18:50     ` Stephen Hemminger
2019-03-04  9:53       ` David Marchand
2019-03-04 11:34     ` David Marchand
2019-03-04 14:33       ` Rastislav Černay
2019-03-04 12:35         ` David Marchand
2019-03-04 12:48           ` David Marchand
2019-03-04 15:15             ` Rastislav Černay
2019-03-05 20:31     ` Rami Rosen
2019-03-05 22:41     ` Luca Boccassi [this message]
2019-03-06 14:51       ` Rastislav Černay
2019-03-06 13:25         ` Luca Boccassi
2019-03-07 13:24   ` [dpdk-dev] [PATCH v4] " Rastislav Cernay
2019-03-07 13:46     ` Luca Boccassi
2019-03-07 14:14       ` Jan Remeš
2019-03-22 12:12   ` [dpdk-dev] [PATCH v5] " Rastislav Cernay
2019-03-22 12:12     ` Rastislav Cernay
2019-03-28 16:01     ` Ferruh Yigit
2019-03-28 16:01       ` Ferruh Yigit
2019-04-01 14:55       ` Rastislav Černay
2019-04-01 14:22         ` Ferruh Yigit
2019-04-01 14:22           ` Ferruh Yigit
2019-04-02 16:05           ` Rastislav Černay
2019-04-02 16:05             ` Rastislav Černay
2019-04-01 14:23         ` Luca Boccassi
2019-04-01 14:23           ` Luca Boccassi
2019-04-01 14:55         ` Rastislav Černay
2019-04-04  9:05   ` [dpdk-dev] [PATCH v6] " Rastislav Cernay
2019-04-04  9:05     ` Rastislav Cernay
2019-04-05  0:08     ` Ferruh Yigit
2019-04-05  0:08       ` Ferruh Yigit
2019-04-07 15:03   ` [dpdk-dev] [PATCH v7] " Rastislav Cernay
2019-04-07 15:03     ` Rastislav Cernay
2019-04-12 12:15     ` Ferruh Yigit
2019-04-12 12:15       ` Ferruh Yigit
2019-04-12 12:16     ` Ferruh Yigit
2019-04-12 12:16       ` Ferruh Yigit
2019-04-12 14:37   ` [dpdk-dev] [PATCH] net/nfb: remove redundant linking Rastislav Cernay
2019-04-12 14:37     ` Rastislav Cernay
2019-04-12 15:02     ` Ferruh Yigit
2019-04-12 15:02       ` 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=130a4780434ea30138a7c98f5689da143c73a8a1.camel@debian.org \
    --to=bluca@debian.org \
    --cc=cernay@netcope.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).