From: "Christian König" <christian.koenig@amd.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] radeon: Use only a single work queue thread for crt
Date: Mon, 7 Sep 2020 10:24:29 +0200 [thread overview]
Message-ID: <3cfac48c-700e-24ce-7677-ca93f7589509@amd.com> (raw)
In-Reply-To: <CAPM=9tw4Md4j95+Zk6LbCZkyj6AFPZSuXacpY3MEabgu20S6Lw@mail.gmail.com>
Am 07.09.20 um 01:47 schrieb Dave Airlie:
> On Sun, 6 Sep 2020 at 18:54, Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> Am 03.08.19 um 02:09 schrieb Andi Kleen:
>>> From: Andi Kleen <ak@linux.intel.com>
>>>
>>> I got tired of seeing a lot of radeon-crt kernel threads in ps on my
>>> workstation, one for each CPU and one for each display, which never use any CPU time.
>>> Surely a single kernel thread is enough to handle the display.
>> NAK, radeon blocks inside the kernel thread and those need to run in
>> parallel or otherwise the hardware can hang.
> Do we need one per cpu? or is one per crtc enough?
One per CRTC is enough, but the patch description sounds like it creates
only a global one.
Christian.
>
> Dave.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-09-07 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 0:09 [PATCH] radeon: Use only a single work queue thread for crt Andi Kleen
2020-09-05 21:56 ` Paul Menzel
2020-09-06 8:53 ` Christian König
2020-09-06 16:02 ` Jan Vesely
2020-09-07 8:25 ` Christian König
2020-09-06 23:47 ` Dave Airlie
2020-09-07 8:24 ` Christian König [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=3cfac48c-700e-24ce-7677-ca93f7589509@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=ak@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andi@firstfloor.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