linux-kernel - Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0704292314180.20994@artax.karlin.mff.cuni.cz>
Date:	Sun, 29 Apr 2007 23:17:10 +0200 (CEST)
From:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To:	Lee Revell <rlrevell@...-job.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS
 is under heavy write load (massive starvation)

On Sat, 28 Apr 2007, Lee Revell wrote:

> On 4/28/07, Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/