[lkml]   [2007]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch 2/2] cpusets: add interleave_over_allowed option
    On Fri, 2007-10-26 at 11:46 -0700, David Rientjes wrote:
    > On Fri, 26 Oct 2007, Lee Schermerhorn wrote:
    > > Actually, my patch doesn't change the set_mempolicy() API at all, it
    > > just co-opts a currently unused/illegal value for the nodemask to
    > > indicate "all allowed nodes". Again, I need to provide a libnuma API to
    > > request this. Soon come, mon...
    > >
    > If something that was previously unaccepted is now allowed with a
    > newly-introduced semantic, that's an API change.

    Well, it's an extension for sure, but a backward compatible one. It
    should not affect any correct existing application--i.e., one that
    checks it's return status--except maybe the odd test program that needs
    to be updated to handle the new semantics. We're allowed to extend APIs
    as long as we don't break correct applications, right?

    I mean, it's not like it's a new argument or such.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-10-26 22:47    [W:0.024 / U:23.752 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site