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: <1182331182.21117.39.camel@twins>
Date:	Wed, 20 Jun 2007 11:19:42 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, davej@...hat.com,
	tim.c.chen@...ux.intel.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: Change in default vm_dirty_ratio

On Wed, 2007-06-20 at 11:14 +0200, Jens Axboe wrote:
> On Wed, Jun 20 2007, Andrew Morton wrote:
> > Perhaps our queues are too long - if the VFS _does_ back off, it'll take
> > some time for that to have an effect.
> > 
> > Perhaps the fact that the queue size knows nothing about the _size_ of the
> > requests in the queue is a problem.
> 
> It's complicated, the size may not matter a lot. 128 sequential 512kb IO
> may complete faster than 128 random 4kb IO's.

Yes, is there any way a queue could be limited to a certain amount of
'completion time' ?

> > Back away even further here.
> > 
> > What user-visible problem(s) are we attemping to fix?
> 
> I'd like innocent-app-doing-little-write-or-fsync not being stalled by
> big-bad-app-doing-lots-of-dirtying.

Could you please try this per BDI dirty limit -v7 patch series, the very
last patch tries to address this by taking the per task dirty rate into
account.

Although, on the fsync, ext3 seems to want to do a global fsync, which
will still make the experience suck. :-(

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