[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230324181936.5sf6xjc5a4vacuku@blackpad>
Date: Fri, 24 Mar 2023 19:19:36 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Will Deacon <will@...nel.org>
Cc: Waiman Long <longman@...hat.com>, Tejun Heo <tj@...nel.org>,
Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Shuah Khan <shuah@...nel.org>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 3/5] cgroup/cpuset: Find another usable CPU if none found
in current cpuset
On Fri, Mar 24, 2023 at 02:32:50PM +0000, Will Deacon <will@...nel.org> wrote:
> So approaches such as killing tasks or rejecting system calls tend not
> to work as well, since you inevitably get divergent behaviour leading
> to functional breakage rather than e.g. performance anomalies.
What about temporary performance drop from 100% to 0% aka freezing the
tasks for the duration of the mismatching affinity config?
> Having said that, the behaviour we currently have in mainline seems to
> be alright, so please don't go out of your way to accomodate these SoCs.
I see. (Just wondering what you think about the fourth option above.)
Thanks,
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists