lkml.org 
[lkml]   [2007]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/2] resource control file system - aka containers on top of nsproxy!
    Paul Jackson wrote:
    >> But "namespace" has well-established historical semantics too - a way
    >> of changing the mappings of local * to global objects. This
    >> accurately describes things liek resource controllers, cpusets, resource
    >> monitoring, etc.
    >>
    >
    > No!
    >
    > Cpusets don't rename or change the mapping of objects.
    >
    > I suspect you seriously misunderstand cpusets and are trying to cram them
    > into a 'namespace' remapping role into which they don't fit.
    >

    Look, you're absolutely right, I'm stretching the terms much too far.

    namespaces implies some kind of domain, which is the namespace, and
    entities within the domain, which are the names, and there is a (task,
    domain) mapping. I was thinking that this implies all similar (task,
    domain) mappings could be treated in the same way. But when you apply
    this to something like cpusets, it gets a little abstract. Like the
    entities are (task,cpu) pairs and the domains the set of cpus that a
    process can run on.

    Sam.
    -
    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: 2007-03-10 09:57    [W:5.216 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site