[lkml]   [2006]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: RFC [patch 13/34] PID Virtualization Define new task_pid api
    On Tue, 2006-01-24 at 21:11 +0000, Alan Cox wrote:
    > On Maw, 2006-01-24 at 12:26 -0700, Eric W. Biederman wrote:
    > > There is at least NFS lockd that appreciates having a single integer
    > > per process unique identifier. So there is a practical basis for
    > > wanting such a thing.
    > Which gets us back to refcounting.
    > > At least for this first round I think talking about a kpid
    > > as a container, pid pair makes a lot of sense for the moment, as
    > > the other implementations just confuse things.
    > As an abstract object a kpid to me means a single identifier which
    > uniquely identifies the process and which in its component parts be they
    > pointers or not uniquely identifies the process in the container and the
    > container in the system, both correctly refcounted against re-use.

    they why not just straight use the task struct pointer for this? It's
    guaranteed unique.. ;)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-01-24 22:18    [W:0.018 / U:48.428 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site