Re: [PATCH 1/2] Customize sched domain via cpuset

[Paul Jackson]

H.Seto wrote:
> So, if there is no one can find use of two flags, I'll change it to one.
> Comments from any others?

I too don't have a strong preference either way ... just a bias toward
keeping the exposed per-cpuset flags as simple and generic as practical.

Exposing internal details that don't need to be exposed has two downsides:
 1) it makes using the flags slightly more difficult, as the user has to
    figure out more details, and
 2) it exposes some internal details that we didn't need to expose, thereby
    possibly making future changes more difficult.  We can change internal
    hidden detail anytime we want, but exposed interfaces are locked in
    with a high barrier to incompatible change.

I too would welcome comments from others.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@xxxxxxx> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/