public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk schedulers
Date: Fri, 15 Feb 2008 17:24:52 +0000	[thread overview]
Message-ID: <47B5CAE4.1000905@grupopie.com> (raw)
In-Reply-To: <20080214162104.GA5347@ics.muni.cz>

Lukas Hejtmanek wrote:
> [...]
> If I'm scping file (about 500MB) from the network (which is faster than the
> local disk), any process is totally unable to read anything from the local disk
> till the scp finishes. It is not caused by low free memory, while scping
> I have 500MB of free memory (not cached or buffered).

If you want to take advantage of all that memory to buffer disk writes, 
so that the reads can proceed better, you might want to tweak your 
/proc/sys/vm/dirty_ratio amd /proc/sys/vm/dirty_background_ratio to more 
appropriate values. (maybe also dirty_writeback_centisecs and 
dirty_expire_centisecs)

You can read all about those tunables in Documentation/filesystems/proc.txt.

Just my 2 cents,

-- 
Paulo Marques - www.grupopie.com

"Very funny Scotty. Now beam up my clothes."

  parent reply	other threads:[~2008-02-15 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 16:21 Disk schedulers Lukas Hejtmanek
2008-02-15  0:02 ` Tejun Heo
2008-02-15 10:09   ` Lukas Hejtmanek
2008-02-15 14:42 ` Jan Engelhardt
2008-02-15 14:57   ` Prakash Punnoor
2008-02-15 17:11     ` Zan Lynx
2008-02-15 21:32       ` FD Cami
2008-02-16 16:13       ` Lukas Hejtmanek
2008-02-20 17:04       ` Zdenek Kabelac
2008-02-15 15:59   ` Lukas Hejtmanek
2008-02-15 16:22     ` Jeffrey E. Hundstad
2008-02-15 17:36     ` Roger Heflin
2008-02-15 17:24 ` Paulo Marques [this message]
2008-02-16 16:15   ` Lukas Hejtmanek
2008-02-16 17:20 ` Pavel Machek
2008-02-20 18:48   ` Lukas Hejtmanek
2008-02-21 23:50     ` Giuliano Pochini
2008-02-17 19:38 ` Linda Walsh
2008-02-28 17:14   ` Bill Davidsen

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=47B5CAE4.1000905@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xhejtman@ics.muni.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox