Message-ID: <87v822ocy2.ffs@tglx>
Date: Fri, 21 Jun 2024 11:35:49 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Tejun Heo <tj@...nel.org>, mingo@...hat.com, peterz@...radead.org,
 juri.lelli@...hat.com, vincent.guittot@...aro.org,
 dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
 mgorman@...e.de, bristot@...hat.com, vschneid@...hat.com, ast@...nel.org,
 daniel@...earbox.net, andrii@...nel.org, martin.lau@...nel.org,
 joshdon@...gle.com, brho@...gle.com, pjt@...gle.com, derkling@...gle.com,
 haoluo@...gle.com, dvernet@...a.com, dschatzberg@...a.com,
 dskarlat@...cmu.edu, riel@...riel.com, changwoo@...lia.com,
 himadrics@...ia.fr, memxor@...il.com, andrea.righi@...onical.com,
 joel@...lfernandes.org, linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
 kernel-team@...a.com
Subject: Re: [PATCHSET v6] sched: Implement BPF extensible scheduler class

Linus!

On Thu, Jun 20 2024 at 12:20, Linus Torvalds wrote:
> On Thu, 20 Jun 2024 at 11:47, Thomas Gleixner <tglx@...utronix.de> wrote:
>> > But I get the very strong feeling that people wanted to limit the
>> > amount of changes they made to the core scheduler code.
>>
>> Which is exactly the point.
>
> But Thomas - that's *MY* point.

You are seriously trying to lecture me of all people about out of tree
code and how it's supposed to be merged?

I really don't know whether I should laugh, cry or just walk away.

> If this code stays out of tree, the goal is always that "don't
> integrate, make the patch easy to apply".

That's absolutely not the goal. The goal is to do a proper and good
integration so that all involved parties can move on.

That's what I clearly said and nothing else.

> This whole "keep things out until they are perfect" is a DISEASE.

Nobody says that things need to be perfect. I'm very much a proponent of
"perfect is the enemy of good".

> It's a disease because it's counter-productive. First off, things will
> never be "perfect" because you have people with different goals in the
> first place.,
>
> But secondly, the "keep things out" is itself counter-productive.

Says the one who kept asking me repeatedly whether I can't keep the
remaining stuff of RT out of tree forever. The last time you asked that
was not that long ago.

Aside of that you are completely ignoring my point.

Collaborative integration is the right thing to do no matter what. I've
integrated and helped many others to integrate tons of controversial
features in the past 20 years so I definitely know what I'm talking
about. But I've also learned my lessons in the past 20 years.

The whole notion of "let's get this in and sort it out later" only works
when people collaborated to begin with and worked on making things more
palatable in the first place. At some point they just agreed to get over
it. That has nothing to do with perfect and keep stuff out of tree
forever.

In all other cases the stuff got merged and the "sort it out later" was
left to those who had the least interest in the so exiting new feature.
They had to mop up the mess to make progress with their own work. I
wasted a substantial portion of my life mopping up the mess which was
declared to be sorted out later and you know that.

If that is your vision of a working and healthy community, then we have
to agree that we disagree.

The issue at hand is clearly both a technical and a social problem.
Contrary to you I don't hate people and my goal is to bridge the rift
which clearly exists. That rift is definitely not helpful to get things
sorted out later in a constructive and collaborative way.

I've offered _my_ time to help and sort this out. That's all I can do.

If you don't care, so be it.

Thanks,

        tglx

Powered by blists - more mailing lists