> +Other fields in the container_subsys object include:
> +- hierarchy: an index indicating which hierarchy, if any, this
> + subsystem is currently attached to. If this is -1, then the
> + subsystem is not attached to any hierarchy, and all tasks should be
> + considered to be members of the subsystem's top_container. It should
> + be initialized to -1.
stale info?
> +struct container {
> + struct containerfs_root *root;
> + struct container *top_container;
> +};
can cont->top_container be different from than &cont->root.top_container?
YAMAMOTO Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
