On Sat, 28 Apr 2007, Lee Revell wrote:
On 4/28/07, Mikulas Patocka <[EMAIL PROTECTED]> wrote:
I most wonder, why vim fsyncs its swapfile regularly (blocking typing
during that) and doesn't fsync the resulting file on :w :-/
Never seen this. Why would fsync block typing unless vim was doing
disk IO for every keystroke?
Lee
Not for every keystroke, but after some time it calls fsync(). During
execution of that call, keyboard is blocked. It is not normally problem
(fsync executes very fastly), but it starts to be problem in case of
extremely overloaded system.
Mikulas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
