Re: la la la la ... swappiness



On Sun, 3 Dec 2006, Andrew Morton wrote:

On Sun, 3 Dec 2006 17:56:30 -0600
"Aucoin" <Aucoin@xxxxxxxxxxxxxx> wrote:

I hope I haven't muddied things up even more but basically what we want to
do is find a way to limit the number of cached pages for disk I/O on the OS
filesystem, even if it drastically slows down the untar and verify process
because the disk I/O we really care about is not on any of the OS
partitions.

Try mounting that fs with `-o sync'.

Wouldn't it be much nicer to just lower the dirty-page limit?

echo 1 > /proc/sys/vm/dirty_background_ratio
echo 2 > /proc/sys/vm/dirty_ratio

or something. Which we already discussed in another thread and almost
already decided we should lower the values for big-mem machines..

Hmm?

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Kill a hanged disk i/o process...
    ... unmount and dumpthe filesystem. ... As I said before disk I/O is irrelevant. ... the completion of the system call, not with data integrity. ... Killing a process with SIGKILL is far from safe. ...
    (freebsd-questions)
  • Re: file.seek and unused bytes
    ... All disk I/O is done in terms of whole blocks ... Whenever the filesystem adds a new block to a file, insteading of ... block in the VFS cache. ...
    (comp.lang.ruby)
  • Re: file.seek and unused bytes
    ... All disk I/O is done in terms of whole blocks ... Whenever the filesystem adds a new block to a file, insteading of ... block in the VFS cache. ...
    (comp.lang.ruby)
  • Re: la la la la ... swappiness
    ... do is find a way to limit the number of cached pages for disk I/O on the OS ... filesystem, even if it drastically slows down the untar and verify process ...
    (Linux-Kernel)