lkml.org 
[lkml]   [2011]   [Nov]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v2 14/14] Change CPUACCT to default n
    From
    Date
    On Fri, 2011-11-25 at 10:05 +0800, Li Zefan wrote:
    > > despite it being a not entirely natural fit. Something I proposed at
    > > Prague and that we could explore here is the idea of a co-mounted
    > > controller. In this example it would only be mountable with cpu so
    > > you could always depend on the cpu hierarchy being there; likewise we
    > > can put (jump-labeled) touchpoints within the cpu-subsystem to call
    > > out for updates as appropriate when the co-mount exists.
    > >
    >
    > IIUC, this co-mounting idea is something I implemented years ago:
    >
    > https://lkml.org/lkml/2008/6/18/389
    >
    > The use case and the reason it was rejected:
    >
    > https://lkml.org/lkml/2008/7/1/97

    "This allows one subsystem to require that it only be mounted when some
    other subsystems are also present in the proposed hierarchy."

    That's not exactly what I meant, what I meant was that say you co-mount
    cpu,cpuset the combined mount provides more features/better performance
    than if you don't. Which then provides a natural incentive to actually
    co-mount the stuff.

    You patch looks like it forces the co-mount.


    \
     
     \ /
      Last update: 2011-11-25 11:13    [W:0.027 / U:29.912 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site