From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kumara Parameshwaran <kparameshwar@vmware.com>,
Kumara Parameshwaran <kumaraparamesh92@gmail.com>,
"keith.wiles@intel.com" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [PATCH] net/tap: Bug fix to populate fds in secondary process
Date: Tue, 18 Jan 2022 09:10:01 +0000 [thread overview]
Message-ID: <c9914123-044e-0cdb-758f-eaac40939362@intel.com> (raw)
In-Reply-To: <SN6PR05MB4895F392E59E2CA24A97AD6BB1589@SN6PR05MB4895.namprd05.prod.outlook.com>
On 1/18/2022 4:39 AM, Kumara Parameshwaran wrote:
>> static int
>> tap_dev_start(struct rte_eth_dev *dev)
>> {
>> int err, i;
>>
>> + tap_mp_req_on_rxtx(dev);
>> +
>
> As for as I understand your logic is primary sends the message to the secondar(y|ies),
> so what happens first secondary is started?
> In case of TAP PMD looks like there is an assumption where primary should be started first. There is an existing check below during the probe function call.
> if (!rte_eal_primary_proc_alive(NULL)) {
> TAP_LOG(ERR, "Primary process is missing");
> return -1;
> }
>
> What about secondary sends the message when they are started?
> IMHO, since primary process setups the queue it should be sufficient for the primary processes to the send the message and secondary need not send anything.
>
> Also above functions is called by both primary and secondary, what happens when it is
> called by secondary? And the logic is not clear, it can be good to add a process type
> check to clarify.
> Sure, these are for tap_intr_handle_set and tap_dev_start functions?
I was thinking within the 'tap_dev_start()' function, for 'tap_mp_req_on_rxtx()' call.
Not sure how 'tap_intr_handle_set()' is involved, am I missing something.
next prev parent reply other threads:[~2022-01-18 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 4:15 [PATCH] net/tap: Bug fix to populate fds in secondary process Kumara Parameshwaran
2022-01-17 18:22 ` Ferruh Yigit
2022-01-18 4:39 ` Kumara Parameshwaran
2022-01-18 9:10 ` Ferruh Yigit [this message]
2022-01-18 10:52 ` kumaraparameshwaran rathinavel
2022-01-18 12:14 ` Ferruh Yigit
2022-01-17 18:28 ` Ferruh Yigit
2022-01-17 18:33 ` Thomas Monjalon
2022-01-18 9:47 ` Ferruh Yigit
2022-01-18 11:21 ` kumaraparameshwaran rathinavel
2022-01-18 12:12 ` Ferruh Yigit
2022-01-18 12:31 ` Thomas Monjalon
2022-01-17 22:16 ` Stephen Hemminger
2022-01-18 5:22 ` Kumara Parameshwaran
2022-01-18 16:21 ` Stephen Hemminger
2022-01-19 4:33 ` kumaraparameshwaran rathinavel
2022-01-19 4:51 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2022-01-21 4:29 Kumara Parameshwaran
2022-01-24 9:47 ` Ferruh Yigit
2022-01-20 13:38 Kumara Parameshwaran
2022-01-20 13:26 Kumara Parameshwaran
2022-01-20 11:12 Kumara Parameshwaran
2022-01-20 15:49 ` Stephen Hemminger
2022-01-24 9:32 ` Ferruh Yigit
2021-11-25 12:25 Kumara Parameshwaran
2021-11-25 12:23 Kumara Parameshwaran
2021-11-25 12:04 Kumara Parameshwaran
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=c9914123-044e-0cdb-758f-eaac40939362@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=kparameshwar@vmware.com \
--cc=kumaraparamesh92@gmail.com \
--cc=rasland@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.