On Tue, Oct 02, 2007 at 12:18:09AM -0700, Andrew Morton wrote:
quoted text
> > > If so, that might be OK - the app just needs a reliable way of working out
> > > whether it's on a 32- or 64-bit kernel?
> > 
> > That would be ugly and a little error prone (would this case really be 
> > tested in user space normally?) but might work.
> 
> I guess it wouldn't be too hard for a 64-bit kernel to fake up 32-bit data
> for 32-bit userspace.  For each architecture :( But let's see what Matt
> thinks.

Grumble. The options are:

a) export it in the kernel's native size and have userspace figure it
out
b) add a header
c) lie to 32-bit apps on 64-bit kernels
d) always export 32 bits
e) always export 64 bits

I started with (a), switched to (b), and then Alan and Dave convinced
me to switch back to (a). I don't think (c) is desireable, especially
as it means having two code paths. (d) would work until memory got
large enough that PFNs didn't fit in 32 bits. (e) would be ok all
around, except for the extra overhead. Ho hum.

-- 
Mathematics is the supreme nostalgia of our time.
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/