Look harder.
Its the default for kernel builds, and the value exported to apps. It was
set at 0x1000000 in 2.1.x before that diff. That meant 2.0 built apps
assuming they could get 0x20000000 byet chunks blew up on 2.1.x and was
a compatibility bug.
Yes you can alter that value up to a gig or more now but the value is
a default. Its probably also a sysctl candidate if anyone feels
inspired
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/