Re: Disabling in-memory write cache for x86-64 in Linux II

From: Diego Calleja
Date: Fri Oct 25 2013 - 15:43:15 EST

El Viernes, 25 de octubre de 2013 18:26:23 Artem S. Tashkinov escribió:
> Oct 25, 2013 05:26:45 PM, david wrote:
> >actually, I think the problem is more the impact of the huge write later
> >on.
> Exactly. And not being able to use applications which show you IO
> performance like Midnight Commander. You might prefer to use "cp -a" but I
> cannot imagine my life without being able to see the progress of a copying
> operation. With the current dirty cache there's no way to understand how
> you storage media actually behaves.

This is a problem I also have been suffering for a long time. It's not so much
how much and when the systems syncs dirty data, but how unreponsive the
desktop becomes when it happens (usually, with rsync + large files). Most
programs become completely unreponsive, specially if they have a large memory
consumption (ie. the browser). I need to pause rsync and wait until the
systems writes out all dirty data if I want to do simple things like scrolling
or do any action that uses I/O, otherwise I need to wait minutes.

I have 16 GB of RAM and excluding the browser (which usually uses about half
of a GB) and KDE itself, there are no memory hogs, so it seem like it's
something that shouldn't happen. I can understand that I/O operations are
laggy when there is some other intensive I/O ongoing, but right now the system
becomes completely unreponsive. If I am unlucky and Konsole also becomes
unreponsive, I need to switch to a VT (which also takes time).

I haven't reported it before in part because I didn't know how to do it, "my
browser stalls" is not a very useful description and I didn't know what kind
of data I'm supposed to report.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at