Only on 32 bit platforms that have High Memory Support enabled.
The sysinfo change to accomodate the fringe (but clearly useful) case of having
64GiB on a 32bit platform breaks source code without making it obvious that the
source code has been broken (not even a compiler warning), and breaks existing
binaries such that the binaries do not notice they have been broken (just wierd
behavior). A segfault would be much more obvious.
How about this: for kernel/info.c I go through a cap each value at ULONG_MAX.
Then I implement kernel/info64.c that provides a new ``sysinfo64'' that returns
sizes in units of PAGE_SIZE. Those that use sysinfo and get ULONG_MAX back for
totalram and friends can then make use of the new ``sysinfo64''. Those wanting
the new behavior can explicitly ask for it (via sysinfo64). This way,
backwords compatability is retainedand nobody gets surprised.
Would this be agreeable?
-Erik
--
Erik B. Andersen Web: http://www.xmission.com/~andersen/
email: andersee@debian.org
--This message was written using 73% post-consumer electrons--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/