mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
	phasta@kernel.org,  Luke.Wildhardt@proton.me
Cc: Danilo Krummrich <dakr@kernel.org>,
	"matthew.brost@intel.com" <matthew.brost@intel.com>,
	"ckoenig.leichtzumerken@gmail.com"
	<ckoenig.leichtzumerken@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] drm/sched: FAIR policy causes serious performance degradation at max GPU load on 9070XT
Date: Wed, 16 Sep 2026 09:37:34 +0200	[thread overview]
Message-ID: <763ba7b5895ac8f850662eaad84a2d5b523a8902.camel@mailbox.org> (raw)
In-Reply-To: <ab60bdb4-351f-4911-9246-2719d078cb96@igalia.com>

On Wed, 2026-08-12 at 13:29 +0100, Tvrtko Ursulin wrote:
> Not sure if you are calling me out here or not, since apart from a 
> direct mention, the lore link above is also a reply to my email, so for 
> the record, I did give my ack for those patches. Plus I spent time 
> testing them. So if you were in fact calling me out, I don't see how 
> that is warranted. And on the wider topic I also never shied away from 
> the non-glamorous work.

I was addressing what I perceive to be the general problems within DRM
– I still believe the general points are valid, but want to stress that
it's a collective problem in which we all play a role, though no one is
the protagonist. I mentioned the media outlet (which quoted your name)
as part of the problem because there are external cheerleaders for
performance (whose unconditional priority is *the* reason for the
design mistakes in drm_sched) and features.

Nevertheless, I apologize for the rough tone and want to emphasize that
you're indeed the most engaged contributor and have improved many
things. The unit tests alone are worth their weight in silver.

The wider, problematic patterns in DRM might be worth addressing with
the appropriate tenderness in a suitable format; I will try to collect
my thoughts on that.


Regards,
Philipp

  reply	other threads:[~2026-09-16  7:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 23:33 Luke.Wildhardt
2026-08-10  8:28 ` Philipp Stanner
2026-08-10 12:45   ` Danilo Krummrich
2026-08-10 13:48     ` Tvrtko Ursulin
2026-08-10 16:40       ` Luke.Wildhardt
2026-08-11  7:29         ` Philipp Stanner
2026-08-11  7:49         ` Tvrtko Ursulin
2026-08-11 17:59         ` Luke.Wildhardt
2026-08-12 11:37           ` Tvrtko Ursulin
2026-08-12 11:58             ` Philipp Stanner
2026-08-12 12:29               ` Tvrtko Ursulin
2026-09-16  7:37                 ` Philipp Stanner [this message]
2026-08-12 15:12             ` Luke.Wildhardt
2026-08-13  6:42               ` Luke.Wildhardt
2026-08-13  7:58                 ` Tvrtko Ursulin
2026-08-13 14:27                   ` Luke.Wildhardt
2026-08-14  6:49                     ` Luke.Wildhardt
2026-08-14  8:32                     ` Feng, Kenneth
2026-08-10 11:36 ` Tvrtko Ursulin
2026-08-11  7:46 ` Tvrtko Ursulin
2026-08-12  4:52   ` Luke.Wildhardt

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=763ba7b5895ac8f850662eaad84a2d5b523a8902.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=Luke.Wildhardt@proton.me \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=tvrtko.ursulin@igalia.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

all inboxes | Powered by JetHome®