Yes there is, since TASO applications need to wrap at 1<<31,
not TASK_SIZE. Note that TASK_SIZE should _not_ be changed
for TASO applications, since they can explicitly map memory
above 4G. An example here is em86, in which the low 4G is
reserved for the emulated program, and the emulator lives in
high memory.
> Patch appended, comments?
I think you're working too hard to make this "efficient", and
in the process making the code hard to read. A subroutine
containing a simple search-forward loop is just as effective.
r~
-
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/