linux-kernel - Re: Change in default vm_dirty

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1182363174.2701.2.camel@laptopd505.fenrus.org>
Date:	Wed, 20 Jun 2007 11:12:53 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Jones <davej@...hat.com>, tim.c.chen@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: Change in default vm_dirty_ratio

On Wed, 2007-06-20 at 10:17 -0700, Linus Torvalds wrote:
> 
> On Wed, 20 Jun 2007, Peter Zijlstra wrote:
> > 
> > Building on the per BDI patches, how about integrating feedback from the
> > full-ness of device queues. That is, when we are happily doing IO and we
> > cannot possibly saturate the active devices (as measured by their queue
> > never reaching 75%?) then we can safely increase the total dirty limit.
> 
> The really annoying things are the one-off things. You've been happily 
> working for a while (never even being _close_ to saturatign any IO 
> queues), and then you untar a large tree.
> 
> If the kernel now let's you dirty lots of memory, you'll have a very 
> unpleasant experience.


maybe that needs to be fixed? If you stopped dirtying after the initial
bump.. is there a reason for the kernel to dump all that data to the
disk in such a way that it disturbs interactive users?

so the question maybe is.. is the vm tunable the cause or the symptom of
the bad experience?


-
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/