DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ed Czeck <ed.czeck@atomicrules.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com,
	John Miller <john.miller@atomicrules.com>,
	Shepard Siegel <shepard.siegel@atomicrules.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [PATCH 1/3] net/ark: support secondary process
Date: Fri, 17 Feb 2023 08:30:06 -0800	[thread overview]
Message-ID: <20230217083006.7e9c1a06@hermes.local> (raw)
In-Reply-To: <20230217154759.2484937-1-ed.czeck@atomicrules.com>

On Fri, 17 Feb 2023 10:47:56 -0500
Ed Czeck <ed.czeck@atomicrules.com> wrote:

> diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
> index b2995427c8..f96722551e 100644
> --- a/drivers/net/ark/ark_ethdev.c
> +++ b/drivers/net/ark/ark_ethdev.c
> @@ -147,6 +147,9 @@ eth_ark_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
>  	struct rte_eth_dev *eth_dev;
>  	int ret;
>  
> +	if (rte_eal_process_type() == RTE_PROC_SECONDARY)
> +		fprintf(stderr, "ARK probed by secondary process\n");

Use standard logging for error messages please.

		ARK_PMD_LOG(DEBUG, "Secondary process probed\n");

  parent reply	other threads:[~2023-02-17 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 15:47 Ed Czeck
2023-02-17 15:47 ` [PATCH 2/3] net/ark: support for single function with multiple port Ed Czeck
2023-02-17 15:47 ` [PATCH 3/3] net/ark: resize data field to match fpga access Ed Czeck
2023-02-17 15:47 ` [PATCH] " Ed Czeck
2023-02-17 16:30 ` Stephen Hemminger [this message]
2023-02-17 16:00 [PATCH 1/3] net/ark: support secondary process Ed Czeck
2023-05-16 15:33 ` Burakov, Anatoly

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=20230217083006.7e9c1a06@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ed.czeck@atomicrules.com \
    --cc=ferruh.yigit@amd.com \
    --cc=john.miller@atomicrules.com \
    --cc=shepard.siegel@atomicrules.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).