From: Patrick Robb <probb@iol.unh.edu>
To: Luca Vizzarro <Luca.Vizzarro@arm.com>
Cc: dev@dpdk.org, dmarx@iol.unh.edu, abailey@iol.unh.edu
Subject: Re: [PATCH] dts: add dpdk shell warm up period
Date: Mon, 8 Sep 2025 09:21:12 -0400 [thread overview]
Message-ID: <CAJvnSUBGaTkbtd7GanHJH9DbOsdFo-imG5joMv61bEpRH=00Xw@mail.gmail.com> (raw)
In-Reply-To: <77838cba-0bf4-4764-8094-664265162081@arm.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Mon, Sep 8, 2025 at 6:03 AM Luca Vizzarro <Luca.Vizzarro@arm.com> wrote:
> Hi Patrick,
>
> Perfectly understand the situation, I am just afraid that adding a whole
> 5 seconds every time an InteractiveShell is spawned may slow down
> everything by a lot. These are spawned a lot of times, so it will stack
> up. Is there no other way to test for readiness?
>
Yeah. I was guessing at the math before and thought it was like +25%
execution time, but now I see it's more like +90%. Definitely not ideal.
I wasn't able to come up with any other readiness checks but maybe there
is. Anyhow let's discuss all this at the Thursday meeting as it's not
urgent.
>
> Also I think we are providing the ability to run shells outside the
> context manager as well for some scenarios where it's needed, so this
> approach won't cover that case unfortunately.
>
Good point I'll take another look.
>
> Best,
> Luca
>
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
prev parent reply other threads:[~2025-09-08 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 1:41 Patrick Robb
2025-09-08 1:57 ` Patrick Robb
2025-09-08 10:03 ` Luca Vizzarro
2025-09-08 13:21 ` Patrick Robb [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='CAJvnSUBGaTkbtd7GanHJH9DbOsdFo-imG5joMv61bEpRH=00Xw@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
/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).