DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>, dev@dpdk.org
Cc: shahar.belkar@huawei.com, luoxianjun@huawei.com,
	xuanziyang2@huawei.com, zhouguoyang@huawei.com,
	wulike1@huawei.com, tanya.brokhman@huawei.com
Subject: Re: [dpdk-dev] [PATCH v6 1/1] net/hinic: fix secondary process issue
Date: Tue, 19 Nov 2019 15:21:59 +0000	[thread overview]
Message-ID: <761977da-a8ee-318a-0e03-d299b130146a@intel.com> (raw)
In-Reply-To: <b30aaa307cd37872cc1dc295591c14addc0ac84b.1574165403.git.cloud.wangxiaoyun@huawei.com>

On 11/19/2019 12:31 PM, Xiaoyun wang wrote:
> The secondary process does not need to register interrupt handle,
> remove rte_intr_callback_register from secondary process branch.
> 
> Fixes: 06b6a81bbabf ("net/hinic: document missing features")

I can see above patch documents the "Multiprocess aware" feature, but not sure
if this patch is a fix for that commit.
Is there any commit that introduces/cause the defect in the code?

> Signed-off-by: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>
> ---
>  drivers/net/hinic/hinic_pmd_ethdev.c | 10 +++-------
>  1 file changed, 3 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/net/hinic/hinic_pmd_ethdev.c b/drivers/net/hinic/hinic_pmd_ethdev.c
> index ddfe082..803a39e 100644
> --- a/drivers/net/hinic/hinic_pmd_ethdev.c
> +++ b/drivers/net/hinic/hinic_pmd_ethdev.c
> @@ -2964,14 +2964,10 @@ static int hinic_func_init(struct rte_eth_dev *eth_dev)
>  
>  	/* EAL is SECONDARY and eth_dev is already created */
>  	if (rte_eal_process_type() != RTE_PROC_PRIMARY) {
> -		rc = rte_intr_callback_register(&pci_dev->intr_handle,
> -						hinic_dev_interrupt_handler,
> -						(void *)eth_dev);
> -		if (rc)
> -			PMD_DRV_LOG(ERR, "Initialize %s failed in secondary process",
> -				    eth_dev->data->name);
> +		PMD_DRV_LOG(INFO, "Initialize %s in secondary process",
> +			    eth_dev->data->name);
>  
> -		return rc;
> +		return 0;
>  	}
>  
>  	nic_dev = HINIC_ETH_DEV_TO_PRIVATE_NIC_DEV(eth_dev);
> 


  reply	other threads:[~2019-11-19 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 12:31 [dpdk-dev] [PATCH v6 0/1] Fix " Xiaoyun wang
2019-11-19 12:31 ` [dpdk-dev] [PATCH v6 1/1] net/hinic: fix " Xiaoyun wang
2019-11-19 15:21   ` Ferruh Yigit [this message]
2019-11-20 12:58     ` 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=761977da-a8ee-318a-0e03-d299b130146a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=luoxianjun@huawei.com \
    --cc=shahar.belkar@huawei.com \
    --cc=tanya.brokhman@huawei.com \
    --cc=wulike1@huawei.com \
    --cc=xuanziyang2@huawei.com \
    --cc=zhouguoyang@huawei.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).