Pavel wrote:
> >> 3. Configfs may be easily implemented later as an additional
> >> interface. I propose the following solution:
> >> ...
> >
> Resource controller has nothing common with confgifs.
> That's the same as if we make netfilter depend on procfs.
Well ... if you used configfs as an interface to resource
controllers, as you said was easily done, then they would
have something to do with each other, right ;)?
Choose the right data structure for the job, and then reuse
what fits for that choice.
Neither avoid nor encouraging code reuse is the key question.
What's the best fit, long term, for the style of kernel-user
API, for this use? That's the key question.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
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]
