I don't think this is a practical solution. It requires cooperation
from all application, i.e. shells. At least the bash authors are
adamant 'not to add more specific API crap for a proprietary and dying
Solaris'.
This is an interesting inflamatory statement to make on a Solaris
list. Google was not able to find any such statement pertaining to
Bash, so I must assume that you must made this up.
I agree that we should *not* have the pipe(2) system call change the system
default... that would be potentially destructive to many applications, as
you note.
The pipe users expect to do atomic writes and reads in chunks of
PIPE_BUF bytes. Increasing the pipe buffer to n*PIPE_BUF (e.g. 5120,
10240, 20480, 40960, ...) is safe.
How could you possibly know this?
More importantly, why is it that ksh93 has a performance problem with
pipes when other shells do not? Is it actually demonstrated to have a
performance problem or is it conjecture?
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
