use of TASK_SIZE to determine user/kernel

[Kumar Gala]

We are looking at a 32-bit architecture implementation were we can have 
distinct address spaces for user and kernel, thus allowing 4G's for 
each.  In doing this we have come across the use of TASK_SIZE to 
determine if an address is user vs kernel (example mm/memory.c).  I'm 
wondering is it just sufficient to set TASK_SIZE to 0xffffffff?  This 
feels wrong to me, since it would imply that all the places that are 
testing will never need access to the kernel memory space.

thanks

- kumar

-
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/