Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: [PATCH] Use line buffering for standard output

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: 2016-06-15 22:45:06


On Sun, 3 Aug 2008, Anders Melchiorsen wrote:
Normally, stdout is fully buffered, unless it refers to a terminal
device. This gives problems when fork() is in play: the buffer is
cloned and output appears twice.

By always setting stdout to line buffering, we make the output work
identically for all output devices.
Please don't.

This is a huge peformance issue for things like

	git log -p > file

where we really want it to be fully buffered.

So please just find the place where we do a fork() without flushing 
pending output...

(We really shouldn't have all that many "fork()" calls left, I thought - 
the Windows stuff means that most of it should be abstracted away. So it's 
not like we're talking about hundreds of sites, there should be just a 
couple).

		Linus
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help