From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Eliot Courtney <ecourtney@nvidia.com>
Cc: Danilo Krummrich <dakr@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Alistair Popple <apopple@nvidia.com>,
Timur Tabi <ttabi@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
nova-gpu@lists.linux.dev, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] gpu: nova-core: gsp: cmdq: do not sleep in wait_for_msg
Date: Fri, 30 Oct 2026 11:32:53 -0700 [thread overview]
Message-ID: <a3bc3e20-4a95-43e1-bda5-cea92d6e6fdc@nvidia.com> (raw)
In-Reply-To: <DMHX5VRNFYLQ.11FZIS5422ZS6@nvidia.com>
On 10/29/26 10:21 PM, Alexandre Courbot wrote:
> On Fri Oct 30, 2026 at 1:32 PM JST, Eliot Courtney wrote:
>> On Fri Oct 30, 2026 at 12:21 PM JST, Alexandre Courbot wrote:
...
>> Previously we had a discussion about Delta::ZERO waits [1] and Danilo
>> had some concerns about creating unnecessary contention by reading
>> coherent memory extremely often. Also, AFAICT `fsleep`'s busy wait is a
>> bit nicer than just spinning. WDYT? I think switching this to
Yes.
>> Delta::from_micros(1) is probably better.
>
> Anything works for me as long as we reduce the spinning-induced latency
> to something reasonable. I'll resping with `from_micros(1)`.
That's good.
thanks,
--
John Hubbard
prev parent reply other threads:[~2026-10-30 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 3:21 [PATCH] gpu: nova-core: gsp: cmdq: do not sleep in wait_for_msg Alexandre Courbot
2026-10-30 4:32 ` Eliot Courtney
2026-10-30 5:21 ` Alexandre Courbot
2026-10-30 18:32 ` John Hubbard [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=a3bc3e20-4a95-43e1-bda5-cea92d6e6fdc@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=zhiw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox