From: Kumara Parameshwaran <kparameshwar@vmware.com>
To: "grive@u256.net" <grive@u256.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Failsafe PMD - Attach to Secondary Process
Date: Fri, 13 Aug 2021 18:47:22 +0000 [thread overview]
Message-ID: <SN6PR05MB4895258BA4D0F079800F64ACB1FA9@SN6PR05MB4895.namprd05.prod.outlook.com> (raw)
Hi,
Recently I was using the failsafe PMD with multi process scenario and found the secondary process was not working as expected. . I saw you were mentioned as the maintainer for this PMD.
I have attached the patch, please let me know if this is okay.
I think in the following commit, the failsafe driver was not changed, but other vdevs were changed.
commit 4852aa8f6e2125664698afc43b820bd787b02756
Date: Tue Oct 16 08:16:30 2018 +0800
drivers/net: enable hotplug on secondary process
Attach port from secondary should ignore devargs since the private
device is not necessary to support. Also previously, detach port on
a secondary process will mess primary process and cause the same
device can't be attached back again. A secondary process should use
rte_eth_dev_release_port_secondary to release a port.
Thanks,
Param.
reply other threads:[~2021-08-13 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=SN6PR05MB4895258BA4D0F079800F64ACB1FA9@SN6PR05MB4895.namprd05.prod.outlook.com \
--to=kparameshwar@vmware.com \
--cc=dev@dpdk.org \
--cc=grive@u256.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).