DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Amr Mokhtar <amr.mokhtar@intel.com>, dev@dpdk.org
Cc: thomas@monjalon.net, anatoly.burakov@intel.com,
	pablo.de.lara.guarch@intel.com, niall.power@intel.com,
	chris.macnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v3 2/5] bbdev: PMD drivers (null/turbo_sw)
Date: Mon, 11 Dec 2017 11:00:08 -0800	[thread overview]
Message-ID: <be674c34-2bf2-aa31-8939-3424dd7c7399@intel.com> (raw)
In-Reply-To: <1512682857-79467-2-git-send-email-amr.mokhtar@intel.com>

On 12/7/2017 1:40 PM, Amr Mokhtar wrote:
> - bbdev 'null' PMD enabled by default
> - bbdev 'turbo_sw' PMD disabled by default

Can you please separate PMDs into their own patches.

> - 'turbo_sw' requires the external FLEXRAN SDK libraries
> 
> Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>

<...>

> +static const struct rte_bbdev_ops pmd_ops = {
> +	.setup_queues = NULL,
> +	.intr_enable = NULL,
> +	.start = NULL,
> +	.stop = NULL,
> +	.close = NULL,

No need to set NULL ones.

<...>

> +RTE_PMD_REGISTER_VDEV(DRIVER_NAME, bbdev_null_pmd_drv);
> +RTE_PMD_REGISTER_ALIAS(DRIVER_NAME, bbdev_null_pmd);

No need to add ALIAS macro, it is for backward compatibility.

> +RTE_PMD_REGISTER_PARAM_STRING(DRIVER_NAME,
> +	BBDEV_NULL_MAX_NB_QUEUES_ARG"=<int> "
> +	BBDEV_NULL_SOCKET_ID_ARG"=<int>");
> +
> +int bbdev_logtype;
> +RTE_INIT(null_bbdev_init_log);
> +static void
> +null_bbdev_init_log(void)
> +{
> +	bbdev_logtype = rte_log_register("pmd.null_bbdev");

What about two layer hierarchy in logtype name, "pmd.bbdev.null" ?

<...>

  reply	other threads:[~2017-12-11 19:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 21:40 [dpdk-dev] [PATCH v3 1/5] bbdev: librte_bbdev library Amr Mokhtar
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 2/5] bbdev: PMD drivers (null/turbo_sw) Amr Mokhtar
2017-12-11 19:00   ` Ferruh Yigit [this message]
2017-12-19 19:09     ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 3/5] bbdev: test applications Amr Mokhtar
2017-12-11 19:01   ` Ferruh Yigit
2017-12-23  0:09     ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 4/5] bbdev: sample app Amr Mokhtar
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 5/5] bbdev: documentation Amr Mokhtar
2017-12-11 19:01   ` Ferruh Yigit
2017-12-19 19:34     ` Mokhtar, Amr
2017-12-18 14:26   ` Kovacevic, Marko
2017-12-23  0:11     ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 0/5] Wireless Baseband Device (bbdev) Amr Mokhtar
2017-12-09  2:44 ` [dpdk-dev] [PATCH v3 1/5] bbdev: librte_bbdev library Ferruh Yigit
2017-12-19 19:03   ` Mokhtar, Amr

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=be674c34-2bf2-aa31-8939-3424dd7c7399@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amr.mokhtar@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=chris.macnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=niall.power@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas@monjalon.net \
    /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).