In a discussion today an alternate idea was proposed by Ben LaHaise. He
suggested creating a POSIX personality, or execution domain. This would
take some pressure off the clone flag space as well as allowing some
optimizations in the code. It could also be used in situations where
POSIX-compatible behavior entails more than just sharing extra resources
between tasks.
This would assume that the resources I'm sharing would only be useful for
POSIX compatibility, but at this point it seems unlikely that anyone would
want to share a subset of them. The resources I'm currently working on
include credentials, signals, and timers, and there's a patch available
for semaphore undo that could also be part of this mechanism.
Since you've made it this far my question to you all is this: assuming
that we do want improved POSIX compatibility does this sound like a
reasonable way to add it?
Thanks,
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
-
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/