Messages in this thread |  | | Date | Thu, 28 Nov 2013 09:45:02 -0500 | From | Tejun Heo <> | Subject | Re: [PATCH]: exec: avoid propagating PF_NO_SETAFFINITY into userspace child |
| |
Hello,
On Thu, Nov 28, 2013 at 03:38:57PM +0100, Peter Zijlstra wrote: > It seems like a perfectly fine interface to me. And much preferable to > creating yet another weird interface to manage tasks.
The problem with that is it isn't an interface where the user specifies what's desired but more of just an exposed facet of implementation details and locks us into either keeping that single parent model for the eternity or doing a shitty hack like extracing attributes from that task if we ever need to change the implementation for whatever reason. In general, it's a much better idea to have an interface where the feature supported is represented explicitly and finitely. If this is something which is actually necessary, I'd vote for having an explicit interface for the desired feature, whatever that may be.
Thanks.
-- tejun
|  |