text: Andrew Morton wrote:>Generally, I think that the whole approach of virtualising the OS so it can>run multiple independent instances of userspace is a good one.>[...]>All of which begs the question "now what?".>[...]>.> >This is a heartening position to hear from someone such as yourself; weseem to be at a near consensus of the way forward.Here's a list based on the one I came up with when I originally startedmy line of development, which got shot down so badly it lost a fewpriority points on my workqueue scheduler :-).0. features that don't need namespaces per sea. Bind Mount Options (mount --bind -o ro, etc)b. FS - immutable linkage invert (immulink)1. core vserver patch - no features (this stuff is succeeded by Serge'sset)a. struct and ps addition; internal API and refcountingb. syscall, and switch (to be canned)c. /proc visibilityd. debugginge. history2. isolation featuresa. IPC, semaphore, and signal restrictionsb. proc/array filteringc. IPv4 chbindd. FS chroot() barriere. general /proc filteringf. ptraceg. process admin: alloc_uid, find_user, sys_setpriority3. virtualisation featuresa. uts informationb. initpid virtualisationc. uptimed. timee. load averagef. ksyslogg. vshelper (reboot support)h. vroot (quota, fs IOCTL, etc)i. general PID virtualisation (eric)j. ngnet (network stack virtualisation)4. resource tracking featuresa. scheduler tracking hookb. FS namespace countingc. FS namespace taggingd. ulimitse. RSS usagef. IO - async tracking5. resource sharing featuresa. scheduling v1 - TBF and vavavoomb. disk scheduler integrationc. RSS limitsd. FS - mad cow6. resource limit featuresa. schedulerb. rlimitsc. disklimits7. super whizzy featuresa. Namespace checkpointingb. Namespace migrationc. HA Cluster Computing (think Tandem)Can anyone see any that are missed?As far as how it is tested etc, I have no particular preferences,whatever people are happy with. I'll continue to track submissions inthe utsl.gen.nz repository:'ll import Serge's new submission there now.Sam.-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to majordomo@vger.kernel.orgMore majordomo info at read the FAQ at