lkml.org 
[lkml]   [2006]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch00/05]: Containers(V2)- Introduction
    From
    Date
    Ar Mer, 2006-09-20 am 10:15 -0700, ysgrifennodd Christoph Lameter:
    > The scalability issues can certainly be managed. See the discussions on
    > linux-mm.

    I'll take a look at a web archive of it, I don't follow -mm.

    > Kernel side resource objects? slab pages? Those are tracked.

    Slab pages isn't a useful tracking tool for two reasons. The first is
    that some resources are genuinely a shared kernel managed pool and
    should be treated that way - thats obviously easy to sort out.

    The second is that slab pages are not the granularity of allocations so
    it becomes possible (and deliberately influencable) to make someone else
    allocate the pages all the time so you don't pay the cost. Hence the
    beancounters track the real objects.

    > Cpusets can share nodes. I am not sure what the problem would be? Paul may
    > be able to give you more details.

    If it can do it in a human understandable way, configured at runtime
    with dynamic sharing, overcommit and reconfiguration of sizes then
    great. Lets see what Paul has to say.

    Alan
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-09-20 19:27    [W:8.180 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site