In io_util.c, readBytes() and writeBytes() use an 8K buffer on the stack.
For platforms with small stacks, these changes can have bad consequences.
Using an 8K stack buffer means we cannot have small stacks and still call
readBytes() (the ARM port of JavaOS uses 8K stacks.)
A read of larger than 8K will do a malloc/free *each* time, which can be slow.
It also means that for very large I/O operations we must have twice as much memory available: n bytes in the Java heap and n bytes in the malloc heap.
dean.long@Eng 1997-08-26
For platforms with small stacks, these changes can have bad consequences.
Using an 8K stack buffer means we cannot have small stacks and still call
readBytes() (the ARM port of JavaOS uses 8K stacks.)
A read of larger than 8K will do a malloc/free *each* time, which can be slow.
It also means that for very large I/O operations we must have twice as much memory available: n bytes in the Java heap and n bytes in the malloc heap.
dean.long@Eng 1997-08-26
- relates to
-
JDK-4134571 java.io: Investigate using non-blocking I/O to save data copying
-
- Open
-