On February 17, 2017 1:10:27 PM PST, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: >On Fri, Feb 17, 2017 at 1:04 PM, Dave Hansen <dave.hansen@xxxxxxxxx> >wrote: >> >> Is this likely to break anything in practice? Nah. But it would >nice >> to avoid it. > >So I go the other way: what *I* would like to avoid is odd code that >is hard to follow. I'd much rather make the code be simple and the >rules be straightforward, and not introduce that complicated >"different address limits" thing at all. > >Then, _if_ we ever find a case where it makes a difference, we could >go the more complex route. But not first implementation, and not >without a real example of why we shouldn't just keep things simple. > > Linus However, we already have different address limits for different threads and/or syscall interfaces - 3 GiB (32-bit with legacy flag), 4 GiB (32-bit or x32), or 128 TiB... and for a while we had a 512 GiB option, too. In that sense an address cap makes sense and generalizes what we already have. It would be pretty hideous for the user, long term, to be artificially restricted to a legacy address cap unless they manage the address space themselves. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
