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: <20190206173228.30e99cf4@lwn.net>
Date:   Wed, 6 Feb 2019 17:32:28 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Quentin Perret <quentin.perret@....com>
Cc:     peterz@...radead.org, rjw@...ysocki.net, juri.lelli@...hat.com,
        mingo@...hat.com, morten.rasmussen@....com, qais.yousef@....com,
        patrick.bellasi@....com, dietmar.eggemann@....com,
        linux-doc@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] Documentation: Explain EAS and EM

On Mon, 21 Jan 2019 11:17:21 +0000
Quentin Perret <quentin.perret@....com> wrote:

> The recently introduced Energy Aware Scheduling (EAS) feature relies on
> a large set of concepts, assumptions, and design choices that are
> probably not obvious for an outsider. Moreover, enabling EAS on a
> particular platform isn't straightforward because of all its
> dependencies. This series tries to address this by introducing proper
> documentation files for the scheduler's part of EAS and for the newly
> introduced Energy Model (EM) framework. These are meant to explain not
> only the design choices of EAS but also to list its dependencies in a
> human-readable location.

So these have been sitting in my folder waiting for acks or some other
sort of discussion, but it's been awfully quiet.  Should I take them, or
do they need further work or ... ?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ