DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Gaëtan Rivet" <grive@u256.net>,
	"Kumara Parameshwaran" <kumaraparamesh92@gmail.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] failsafe: Bug fix for the secondary process RX-TX support
Date: Wed, 17 Nov 2021 11:26:11 +0000	[thread overview]
Message-ID: <d1d9c520-28aa-1fe9-b1d4-3c40f535d27f@intel.com> (raw)
In-Reply-To: <701ff4b4-5350-4e96-a4d4-3e178c71bce3@www.fastmail.com>

On 11/11/2021 10:59 AM, Gaëtan Rivet wrote:
> On Thu, Nov 11, 2021, at 11:06, Kumara Parameshwaran wrote:
>> Remove the vdev args check for secondary process which prevents the
>> secondary from attaching
>> to the device created by the primary process via the hotplug framework.
>> This check was removed
>> for other vdevs but was missed for failsafe.
>>
>> Signed-off-by: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
> 
> Hello Kumara,
> 
> Thanks for your patch.
> If this is a fix, can you provide the fixline with a pointer to the patch it is meant
> to fix please?
> 
> I'm guessing this should be this:
> Fixes: 4852aa8f6e21 ("drivers/net: enable hotplug on secondary process")
> Cc: qi.z.zhang@intel.com
> 
> Looking at this patch, I see also
> 
> +       if (rte_eal_process_type() != RTE_PROC_PRIMARY)
> +               return rte_eth_dev_release_port_secondary(eth_dev);
> +
> 
> Added to the remove callbacks of the ports.
> It seems to be omitted from this patch, is there a reason?
> 

Hi Gaetan,

Above addition is no more required since primary and secondary release
functions merged into 'rte_eth_dev_release_port()' one which has process
type check inside it.

And failsafe remove path already calls 'rte_eth_dev_release_port()', so
it should be OK.

>> ---
>>   drivers/net/failsafe/failsafe.c | 3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/failsafe/failsafe.c b/drivers/net/failsafe/failsafe.c
>> index ad6b43538e..3c754a5f66 100644
>> --- a/drivers/net/failsafe/failsafe.c
>> +++ b/drivers/net/failsafe/failsafe.c
>> @@ -340,8 +340,7 @@ rte_pmd_failsafe_probe(struct rte_vdev_device *vdev)
>>   	INFO("Initializing " FAILSAFE_DRIVER_NAME " for %s",
>>   			name);
>>
>> -	if (rte_eal_process_type() == RTE_PROC_SECONDARY &&
>> -	    strlen(rte_vdev_device_args(vdev)) == 0) {
>> +	if (rte_eal_process_type() == RTE_PROC_SECONDARY) {
>>   		eth_dev = rte_eth_dev_attach_secondary(name);
>>   		if (!eth_dev) {
>>   			ERROR("Failed to probe %s", name);
>> -- 
>> 2.30.1 (Apple Git-130)
> 


  reply	other threads:[~2021-11-17 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 10:06 Kumara Parameshwaran
2021-11-11 10:59 ` Gaëtan Rivet
2021-11-17 11:26   ` Ferruh Yigit [this message]
2021-11-11 11:51 Kumara Parameshwaran
2021-11-11 12:44 Kumara Parameshwaran
2021-11-17 12:04 ` 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=d1d9c520-28aa-1fe9-b1d4-3c40f535d27f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=grive@u256.net \
    --cc=kumaraparamesh92@gmail.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).