From: Stephen Hemminger <stephen@networkplumber.org>
To: Gabor LENCSE <lencse@hit.bme.hu>
Cc: users@dpdk.org
Subject: Re: rte_exit() does not terminate the program -- is it a bug or a new feature?
Date: Mon, 18 Sep 2023 11:49:50 -0700 [thread overview]
Message-ID: <20230918114950.6be79839@hermes.local> (raw)
In-Reply-To: <9d41e20b-f0b9-eba0-484c-8bafc96c5ca9@hit.bme.hu>
On Mon, 18 Sep 2023 20:23:25 +0200
Gabor LENCSE <lencse@hit.bme.hu> wrote:
> Of course, I will review all my rte_exit calls... It'll take a while...
>
> I am just curious, as I have no idea, why my old code worked all right
> with DPDK 16.11. Has rte_exit() been changed since then?
Older versions of the DPDK did not call eal_cleanup() and did not
have service lcores. I think service lcores were new in 18.11
prev parent reply other threads:[~2023-09-18 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 8:24 Gabor LENCSE
2023-09-15 15:06 ` Stephen Hemminger
2023-09-15 18:28 ` Gabor LENCSE
2023-09-15 21:33 ` Stephen Hemminger
2023-09-17 19:37 ` Gabor LENCSE
2023-09-17 21:27 ` Stephen Hemminger
2023-09-18 18:23 ` Gabor LENCSE
2023-09-18 18:49 ` Stephen Hemminger [this message]
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=20230918114950.6be79839@hermes.local \
--to=stephen@networkplumber.org \
--cc=lencse@hit.bme.hu \
--cc=users@dpdk.org \
/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).