From: Robert Hable <Robert.Hable@spusu.at>
To: Dmitry Malloy <dmitrym@microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Narcisa Ana Maria Vasile <Narcisa.Vasile@microsoft.com>
Subject: AW: [EXTERNAL] Re: Windows rte_pktmbuf_pool_create() ENOMEM
Date: Thu, 15 Dec 2022 16:14:42 +0000 [thread overview]
Message-ID: <PAXP190MB1741D563143176B79DA6B52BE1E19@PAXP190MB1741.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <PH0PR21MB1941F3007123082DF675B961B31A9@PH0PR21MB1941.namprd21.prod.outlook.com>
Hello,
Sure, I will turn on all tracing and add some extra tracing myself. I am currently trying to reproduce the problem, but until now it just happens randomly after some longer uptime.
I will send traces as soon as I can reproduce the error.
Regards,
Robert
-----Ursprüngliche Nachricht-----
Von: Dmitry Malloy <dmitrym@microsoft.com>
Gesendet: Mittwoch, 7. Dezember 2022 22:14
An: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>; Robert Hable <Robert.Hable@spusu.at>
Cc: users@dpdk.org; Tyler Retzlaff <roretzla@linux.microsoft.com>; Narcisa Ana Maria Vasile <Narcisa.Vasile@microsoft.com>
Betreff: RE: [EXTERNAL] Re: Windows rte_pktmbuf_pool_create() ENOMEM
In order for us to raise this with proper team at MSFT, we need better diagnosis that "likely".
Robert - can you enable any existing DPDK instrumentation/traces, or add more custom tracing for your setup to narrow down the root-cause?
Thank You,
Dmitry
-----Original Message-----
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Sent: Wednesday, December 7, 2022 7:50 AM
To: Robert Hable <Robert.Hable@spusu.at>
Cc: users@dpdk.org; Tyler Retzlaff <roretzla@linux.microsoft.com>; Dmitry Malloy <dmitrym@microsoft.com>; Narcisa Ana Maria Vasile <Narcisa.Vasile@microsoft.com>
Subject: [EXTERNAL] Re: Windows rte_pktmbuf_pool_create() ENOMEM
Hi Robert,
2022-12-07 15:19 (UTC+0000), Robert Hable:
> after a few days of my windows machine running and starting/stopping my DPDK application multiple times, rte_pktmbuf_pool_create() fails with rte_error = EMOM.
> When closing most of the running programs on that machine, it usually works again for some time. I assume this happens because of memory fragmentation?
> What can I do against this error, except just rebooting the whole machine every time and closing applications all the time?
Yes, fragmentation is likely the cause.
Adding Microsoft people who might know how to prevent this, since I don't.
prev parent reply other threads:[~2022-12-15 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 15:19 Robert Hable
2022-12-07 15:50 ` Dmitry Kozlyuk
2022-12-07 21:13 ` [EXTERNAL] " Dmitry Malloy
2022-12-15 16:14 ` Robert Hable [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=PAXP190MB1741D563143176B79DA6B52BE1E19@PAXP190MB1741.EURP190.PROD.OUTLOOK.COM \
--to=robert.hable@spusu.at \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=roretzla@linux.microsoft.com \
--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).