LKML Archive on
help / color / mirror / Atom feed
From: Leroy van Logchem <>
Subject: Re: [PATCH - RFC] allow setting vm_dirty below 1% for large memory machines
Date: Wed, 7 Mar 2007 10:23:14 +0000 (UTC)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> > actually a global dirty_ratio causes interference between devices which 
> > should otherwise not block each other...
> > 
> > if you set up a "dd if=/dev/zero of=/dev/sdb bs=1M" it shouldn't affect 
> > write performance on sda -- but it does... because the dd basically 
> > dirties all of the "dirty_background_ratio" pages and then any task 
> > writing to sda has to block in the foreground...  (i've had this happen in 
> > practice -- my hack fix is oflag=direct on the dd... but the problem still 
> > exists.)
> yeah.  Plus your heavy-dd-to-/dev/sda tends to block light-writers to
> /dev/sda in perhaps disproportionate ways.
> This is on my list of things to look at.  Hah.

It really exists in the wild on both large memory and storage machines. I hope
we don't have to patch Samba on every release to add POSIX fadvise calls in
order to have a more polite VM. A 'cfq' for write generators from vm to devices
would be nice if it can auto probe the device write speed so we don't have to
use knobs. Just let the kernel figure out what are the best values to the
algorithms would be the ideal world.

      reply	other threads:[~2007-03-07 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  8:57 Neil Brown
2007-01-09 10:10 ` Andrew Morton
2007-01-10  3:04   ` Neil Brown
2007-01-10  3:29   ` Neil Brown
2007-01-10  3:41     ` Andrew Morton
2007-01-11 11:04 ` dean gaudet
2007-01-11 20:21   ` Andrew Morton
2007-01-11 22:35     ` dean gaudet
2007-01-11 22:48       ` Andrew Morton
2007-03-07 10:23         ` Leroy van Logchem [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: [PATCH - RFC] allow setting vm_dirty below 1% for large memory machines' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).