Quoting r. Nick Piggin <[EMAIL PROTECTED]>: > Subject: Re: [Fwd: Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK] > > Nick Piggin wrote: > > >All I'm saying is that we can easily wait a few days until arch > >maintainers have had a chance to comment (you didn't think you > >were missing anything last time, either). > > > >We can afford to be a little bit careful about changing user APIs. > > > > If it is a good idea to keep the common MADV_ parameters in synch > over all architectures, why not make 0x00 - 0xff the legacy space, > then 0x100 - 0xfff can be for arch specific parameters, and > 0x1000 - ... can be for common/generic parameters?
Sounds good to me. How about we change MADV_REMOVE to fall in this range too, then? -- Michael S. Tsirkin Staff Engineer, Mellanox Technologies - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
