From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
Ori Kam <orika@mellanox.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
"Kantecki, Tomasz" <tomasz.kantecki@intel.com>,
Sunil Kumar Kori <skori@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 10/11] examples/l3fwd: add graceful teardown for eventdevice
Date: Tue, 7 Jan 2020 16:28:04 +0000 [thread overview]
Message-ID: <CY4PR1801MB1863A1E4FC8B1799AAD6E746DE3F0@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB25581F4B7976A09A585429309A3C0@SN6PR11MB2558.namprd11.prod.outlook.com>
>-----Original Message-----
>From: Ananyev, Konstantin <konstantin.ananyev@intel.com>
>Sent: Monday, January 6, 2020 5:43 PM
>To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Jerin
>Jacob Kollanukkaran <jerinj@marvell.com>; Kovacevic, Marko
><marko.kovacevic@intel.com>; Ori Kam <orika@mellanox.com>;
>Richardson, Bruce <bruce.richardson@intel.com>; Nicolau, Radu
><radu.nicolau@intel.com>; Akhil Goyal <akhil.goyal@nxp.com>;
>Kantecki, Tomasz <tomasz.kantecki@intel.com>; Sunil Kumar Kori
><skori@marvell.com>
>Cc: dev@dpdk.org
>Subject: [EXT] RE: [dpdk-dev] [PATCH v2 10/11] examples/l3fwd: add
>graceful teardown for eventdevice
>
>External Email
>
>----------------------------------------------------------------------
>
>> >> Add graceful teardown that addresses both event mode and poll
>> >mode.
>> >>
>> >> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>> >> ---
>> >> examples/l3fwd/main.c | 49
>++++++++++++++++++++++++++++++-
>> >------------
>> >> 1 file changed, 34 insertions(+), 15 deletions(-)
>> >>
>> >> diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
>> >> index 0ae64dd41..68998f42c 100644
>> >> --- a/examples/l3fwd/main.c
>> >> +++ b/examples/l3fwd/main.c
>> >> @@ -920,7 +920,7 @@ main(int argc, char **argv)
>> >> struct lcore_conf *qconf;
>> >> struct rte_eth_dev_info dev_info;
>> >> struct rte_eth_txconf *txconf;
>> >> - int ret;
>> >> + int i, ret;
>> >> unsigned nb_ports;
>> >> uint16_t queueid, portid;
>> >> unsigned lcore_id;
>> >> @@ -1195,27 +1195,46 @@ main(int argc, char **argv)
>> >> }
>> >> }
>> >>
>> >> -
>> >> check_all_ports_link_status(enabled_port_mask);
>> >>
>> >> ret = 0;
>> >> /* launch per-lcore init on every lcore */
>> >> rte_eal_mp_remote_launch(l3fwd_lkp.main_loop, NULL,
>> >CALL_MASTER);
>> >> - RTE_LCORE_FOREACH_SLAVE(lcore_id) {
>> >> - if (rte_eal_wait_lcore(lcore_id) < 0) {
>> >> - ret = -1;
>> >> - break;
>> >> + if (evt_rsrc->enabled) {
>> >> + for (i = 0; i < evt_rsrc->rx_adptr.nb_rx_adptr; i++)
>> >> + rte_event_eth_rx_adapter_stop(
>> >> + evt_rsrc->rx_adptr.rx_adptr[i]);
>> >> + for (i = 0; i < evt_rsrc->tx_adptr.nb_tx_adptr; i++)
>> >> + rte_event_eth_tx_adapter_stop(
>> >> + evt_rsrc->tx_adptr.tx_adptr[i]);
>> >> +
>> >> + RTE_ETH_FOREACH_DEV(portid) {
>> >> + if ((enabled_port_mask & (1 << portid)) == 0)
>> >> + continue;
>> >> + rte_eth_dev_stop(portid);
>> >> }
>> >> - }
>> >>
>> >> - /* stop ports */
>> >> - RTE_ETH_FOREACH_DEV(portid) {
>> >> - if ((enabled_port_mask & (1 << portid)) == 0)
>> >> - continue;
>> >> - printf("Closing port %d...", portid);
>> >> - rte_eth_dev_stop(portid);
>> >> - rte_eth_dev_close(portid);
>> >> - printf(" Done\n");
>> >
>> >Why to stop ports *before* making sure all lcores are stopped?
>> >Shouldn't that peace of code be identical for both poll and event
>mode?
>> >Something like:
>> >rte_eal_mp_wait_lcore();
>> >
>> > RTE_ETH_FOREACH_DEV(portid) {
>> > if ((enabled_port_mask & (1 << portid)) == 0)
>> > continue;
>> > rte_eth_dev_stop(portid);
>> > rte_eth_dev_close(portid);
>> > }
>> >?
>> >
>>
>> Event dev spec requires stopping producers before consumers else
>we might run into
>> deadlock in some cases.
>
>Ok... but for TX path wouldn't core be a producer?
Not in all cases, true in case of SW event device and implementation defined in HW event devices.
Also both the cases of Tx poll on force_quit in case Tx path fails so that cores can exit.
if (flags & L3FWD_EVENT_TX_ENQ) {
ev.queue_id = tx_q_id;
ev.op = RTE_EVENT_OP_FORWARD;
while (rte_event_enqueue_burst(event_d_id, event_p_id,
&ev, 1) && !force_quit)
;
}
if (flags & L3FWD_EVENT_TX_DIRECT) {
rte_event_eth_tx_adapter_txq_set(mbuf, 0);
while (!rte_event_eth_tx_adapter_enqueue(event_d_id,
event_p_id, &ev, 1, 0) &&
!force_quit)
;
}
>Also for that wouldn't rte_event_eth_(rx|tx)_adapter_stop(0 be
>enough?
In case of HW event devices the above might be nop as control lies with driver/net.
And since anyway we need to stop ethernet device we might as well do it here.
>I am not familiar with event-dev spec at all, so forgive for possibly dumb
>questions 😉
😊
>
>>
>> >> + rte_eal_mp_wait_lcore();
>> >> + RTE_ETH_FOREACH_DEV(portid) {
>> >> + if ((enabled_port_mask & (1 << portid)) == 0)
>> >> + continue;
>> >> + rte_eth_dev_close(portid);
>> >> + }
>> >> +
>> >> + rte_event_dev_stop(evt_rsrc->event_d_id);
>> >> + rte_event_dev_close(evt_rsrc->event_d_id);
>> >> +
>> >> + } else {
>> >> + rte_eal_mp_wait_lcore();
>> >> +
>> >> + RTE_ETH_FOREACH_DEV(portid) {
>> >> + if ((enabled_port_mask & (1 << portid)) == 0)
>> >> + continue;
>> >> + printf("Closing port %d...", portid);
>> >> + rte_eth_dev_stop(portid);
>> >> + rte_eth_dev_close(portid);
>> >> + printf(" Done\n");
>> >> + }
>> >> }
>> >> printf("Bye...\n");
>> >>
>> >> --
>> >> 2.17.1
next prev parent reply other threads:[~2020-01-07 16:28 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 14:43 [dpdk-dev] [PATCH v2 00/11] example/l3fwd: introduce event device support pbhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 01/11] examples/l3fwd: add framework for event device pbhagavatula
2020-01-03 12:49 ` Ananyev, Konstantin
2020-01-06 4:27 ` Pavan Nikhilesh Bhagavatula
2020-01-06 12:32 ` Ananyev, Konstantin
2020-01-07 16:34 ` Pavan Nikhilesh Bhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 02/11] examples/l3fwd: split pipelines based on capability pbhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 03/11] examples/l3fwd: add event device configuration pbhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 04/11] examples/l3fwd: add ethdev setup based on eventdev pbhagavatula
2019-12-27 13:33 ` Nipun Gupta
2019-12-29 15:42 ` Pavan Nikhilesh Bhagavatula
2019-12-30 7:40 ` Nipun Gupta
2020-01-02 6:21 ` Pavan Nikhilesh Bhagavatula
2020-01-02 8:49 ` Nipun Gupta
2020-01-02 9:33 ` Jerin Jacob
2020-01-03 9:06 ` Nipun Gupta
2020-01-03 9:09 ` Jerin Jacob
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 05/11] examples/l3fwd: add event port and queue setup pbhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 06/11] examples/l3fwd: add event eth Rx/Tx adapter setup pbhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 07/11] examples/l3fwd: add service core setup based on caps pbhagavatula
2020-01-03 13:07 ` Ananyev, Konstantin
2020-01-06 4:29 ` Pavan Nikhilesh Bhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 08/11] examples/l3fwd: add event lpm main loop pbhagavatula
2020-01-03 13:16 ` Ananyev, Konstantin
2020-01-06 4:43 ` Pavan Nikhilesh Bhagavatula
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 09/11] examples/l3fwd: add event em " pbhagavatula
2020-01-03 13:45 ` Ananyev, Konstantin
2020-01-06 4:44 ` Pavan Nikhilesh Bhagavatula
2020-01-06 12:27 ` Ananyev, Konstantin
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 10/11] examples/l3fwd: add graceful teardown for eventdevice pbhagavatula
2020-01-03 13:52 ` Ananyev, Konstantin
2020-01-06 4:50 ` Pavan Nikhilesh Bhagavatula
2020-01-06 12:12 ` Ananyev, Konstantin
2020-01-07 16:28 ` Pavan Nikhilesh Bhagavatula [this message]
2019-12-04 14:43 ` [dpdk-dev] [PATCH v2 11/11] doc: update l3fwd user guide to support eventdev pbhagavatula
2019-12-04 15:16 ` [dpdk-dev] [PATCH v2 00/11] example/l3fwd: introduce event device support Jerin Jacob
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 " pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 01/11] examples/l3fwd: add framework for event device pbhagavatula
2020-01-21 8:44 ` Jerin Jacob
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 02/11] examples/l3fwd: split pipelines based on capability pbhagavatula
2020-01-21 8:46 ` Jerin Jacob
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 03/11] examples/l3fwd: add event device configuration pbhagavatula
2020-01-21 8:51 ` Jerin Jacob
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 04/11] examples/l3fwd: add ethdev setup based on eventdev pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 05/11] examples/l3fwd: add event port and queue setup pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 06/11] examples/l3fwd: add event eth Rx/Tx adapter setup pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 07/11] examples/l3fwd: add service core setup based on caps pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 08/11] examples/l3fwd: add event lpm main loop pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 09/11] examples/l3fwd: add event em " pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 10/11] examples/l3fwd: add graceful teardown for eventdevice pbhagavatula
2020-01-11 13:47 ` [dpdk-dev] [PATCH v3 11/11] doc: update l3fwd user guide to support eventdev pbhagavatula
2020-01-13 12:02 ` [dpdk-dev] [PATCH v3 00/11] example/l3fwd: introduce event device support Nipun Gupta
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 " pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 01/11] examples/l3fwd: add framework for event device pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 02/11] examples/l3fwd: split pipelines based on capability pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 03/11] examples/l3fwd: add event device configuration pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 04/11] examples/l3fwd: add ethdev setup based on eventdev pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 05/11] examples/l3fwd: add event port and queue setup pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 06/11] examples/l3fwd: add event eth Rx/Tx adapter setup pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 07/11] examples/l3fwd: add service core setup based on caps pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 08/11] examples/l3fwd: add event lpm main loop pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 09/11] examples/l3fwd: add event em " pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 10/11] examples/l3fwd: add graceful teardown for eventdevice pbhagavatula
2020-01-22 18:28 ` [dpdk-dev] [PATCH v4 11/11] doc: update l3fwd user guide to support eventdev pbhagavatula
2020-01-23 5:25 ` Jerin Jacob
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 00/11] example/l3fwd: introduce event device support pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 01/11] examples/l3fwd: add framework for event device pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 02/11] examples/l3fwd: split pipelines based on capability pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 03/11] examples/l3fwd: add event device configuration pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 04/11] examples/l3fwd: add ethdev setup based on eventdev pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 05/11] examples/l3fwd: add event port and queue setup pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 06/11] examples/l3fwd: add event eth Rx/Tx adapter setup pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 07/11] examples/l3fwd: add service core setup based on caps pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 08/11] examples/l3fwd: add event lpm main loop pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 09/11] examples/l3fwd: add event em " pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 10/11] examples/l3fwd: add graceful teardown for eventdevice pbhagavatula
2020-01-24 4:05 ` [dpdk-dev] [PATCH v5 11/11] doc: update l3fwd user guide to support eventdev pbhagavatula
2020-01-27 16:17 ` [dpdk-dev] [PATCH v5 00/11] example/l3fwd: introduce event device support Jerin Jacob
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=CY4PR1801MB1863A1E4FC8B1799AAD6E746DE3F0@CY4PR1801MB1863.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=orika@mellanox.com \
--cc=radu.nicolau@intel.com \
--cc=skori@marvell.com \
--cc=tomasz.kantecki@intel.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).