* use of TASK_SIZE to determine user/kernel
@ 2005-02-18 17:04 Kumar Gala
0 siblings, 0 replies; only message in thread
From: Kumar Gala @ 2005-02-18 17:04 UTC (permalink / raw)
To: Linux Kernel list; +Cc: Becky Gill
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-02-18 17:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-18 17:04 use of TASK_SIZE to determine user/kernel Kumar Gala
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).