linux-kernel - Re: [RFC][PATCH 3/3] sched: User Mode Concurency Groups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YefRLYwKy0AeHyhz@hirez.programming.kicks-ass.net>
Date:   Wed, 19 Jan 2022 09:51:57 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Peter Oskolkov <posk@...gle.com>
Cc:     Peter Oskolkov <posk@...k.io>, mingo@...hat.com,
        tglx@...utronix.de, juri.lelli@...hat.com,
        vincent.guittot@...aro.org, dietmar.eggemann@....com,
        rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
        bristot@...hat.com, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, linux-api@...r.kernel.org, x86@...nel.org,
        pjt@...gle.com, avagin@...gle.com, jannh@...gle.com,
        tdelisle@...terloo.ca
Subject: Re: [RFC][PATCH 3/3] sched: User Mode Concurency Groups

On Tue, Jan 18, 2022 at 10:19:21AM -0800, Peter Oskolkov wrote:

> ================ worker timeouts
> 
> Timeouts now are easy to explain: mutex::lock() and condvar::wait() have
> timeouts, so workers waiting on these primitives naturally wait with timeouts;
> if sys_umcg_wait() supports worker timeouts, this is it, all is simple; if
> it does not, the userspace now has to implement the whole timeout machinery,
> in order to wake these sleeping workers when their timeouts expire.

I still have absolutely no idea what you're on about here. Please reply
to the email on that subject:

  https://lkml.kernel.org/r/Ya34S2JCQg+81h4t@hirez.programming.kicks-ass.net

What would you have the timeout actually do? Talk about the state
transitions.