Hi! > >> (It does seem unfortunate that the man page cannot help the programmer > >> actually write correct code here. He or she is forced to read the kernel > >> implementation, in order to figure out the true alignment rules. I was > >> hoping we could avoid that.) > > > > It would be nice if we had this information exported somehere so that we > > do not have to rely on per-architecture ifdefs. > > > > What about adding MapAligment or something similar to the /proc/meminfo? > > > > What's the use case you envision for that? I don't see how that would be > better than using SHMLBA, which is available at compiler time. Because > unless someone expects to be able to run an app that was compiled for > Arch X, on Arch Y (surely that's not requirement here?), I don't see how > the run-time check is any better. I guess that some kind of compile time constant in uapi headers will do as well, I'm really open to any solution that would expose this constant as some kind of official API. There is one problem with using SHMLBA, there are more than one libc implementations and at least two of them (bionic and klibc) does not implement the SysV IPC at all. I know that the chances that you are writing a program that requires MAP_FIXED, is compiled against alternative libc, and expected to run on less common architectures are pretty slim. On the other hand I do not see a reason why this cannot be done properly, this is just about exporting one simple constant to userspace after all. > Or maybe you're thinking that since the SHMLBA cannot be put in the man > pages, we could instead provide MapAlignment as sort of a different > way to document the requirement? This is my intention as well. -- Cyril Hrubis chrubis@xxxxxxx -- 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
