Re: [ANNOUNCE] linux-libc-headers 2.6.8.1
From: Erik Andersen
Date: Mon Aug 30 2004 - 01:30:01 EST
On Sun Aug 29, 2004 at 10:32:13PM +0200, Mariusz Mazur wrote:
> Nothing special, really. One bigger change - on archs that have >1 possible
> page sizes (PAGE_SIZE definition in asm/page.h) we're now using a call to
> libc's getpagesize(), so don't count on it being static on archs like ia64.
I really do not like this change. Since PAGE_SIZE has always
been a constant, the change you have made is likely to break a
fair amount of code, basically any code doing stuff like:
static int* foo[PAGE_SIZE];
Your change will result in cryptic errors such as
"error: variable-size type declared outside of any function"
"error: storage size of `foo' isn't constant"
depending on whether the declaration is outside a function or in one.
I think it would be much better to either
a) remove PAGE_SIZE or make using it an error somehow,
b) make PAGE_SIZE an install time config option
c) declare that on architectures such as mips that support
variable PAGE_SIZE values, the libc kernel headers shall
always provide the largest fixed size value of PAGE_SIZE
supported for that architecture and everyone just agrees
that using PAGE_SIZE rather than getpagesize(2) or
sysconf(_SC_PAGESIZE) is generally a bad idea. It should
be the largest value supported on that architecture, since
the the only cost of always using the largest possible
value is wasted ram, whereas the cost of always using the
smallest value is segfaults.
With any of the above 3 suggestions, things will either just
work, or the user will get a descriptive error message.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/