lkml.org 
[lkml]   [2019]   [Jul]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH 1/6] sched/dl: Improve deadline admission control for asymmetric CPU capacities
    On Monday 08 Jul 2019 at 13:22:35 (+0200), Dietmar Eggemann wrote:
    > On 5/7/19 4:43 PM, luca abeni wrote:
    > > On Tue, 7 May 2019 15:31:27 +0100
    > > Quentin Perret <quentin.perret@arm.com> wrote:
    > >
    > >> On Tuesday 07 May 2019 at 16:25:23 (+0200), luca abeni wrote:
    > >>> On Tue, 7 May 2019 14:48:52 +0100
    > >>> Quentin Perret <quentin.perret@arm.com> wrote:
    > >>>
    > >>>> Hi Luca,
    > >>>>
    > >>>> On Monday 06 May 2019 at 06:48:31 (+0200), Luca Abeni wrote:
    >
    > [...]
    >
    > >> Right and things moved recently in this area, see bb1fbdd3c3fd
    > >> ("sched/topology, drivers/base/arch_topology: Rebuild the sched_domain
    > >> hierarchy when capacities change")
    > >
    > > Ah, thanks! I missed this change when rebasing the patchset.
    > > I guess this part of the patch has to be updated (and probably became
    > > useless?), then.
    >
    > [...]
    >
    > >>> This achieved the effect of correctly setting up the "rd_capacity"
    > >>> field, but I do not know if there is a better/simpler way to achieve
    > >>> the same result :)
    > >>
    > >> OK, that's really an implementation detail, so no need to worry too
    > >> much about it at the RFC stage I suppose :-)
    >
    > What about we integrate the code to calculate the rd capacity into
    > build_sched_domains() (next to the code to establish the rd
    > max_cpu_capacity)?

    Right, that's also what Vincent suggested IIRC. I think that'd work :)

    Thanks,
    Quentin

    \
     
     \ /
      Last update: 2019-07-08 17:06    [W:2.894 / U:0.548 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site