From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu,
piggin@cyberone.com.au, kernel@kolivas.org, linux-mm@kvack.org
Subject: Re: [patch] real-time enhanced page allocator and throttling
Date: 06 Aug 2003 10:01:14 -0700 [thread overview]
Message-ID: <1060189274.4494.212.camel@localhost> (raw)
In-Reply-To: <20030806014148.5408cfbd.akpm@osdl.org>
On Wed, 2003-08-06 at 01:41, Andrew Morton wrote:
> It's pretty easy to demonstrate the benefit of the balance_dirty_pages()
> change. Just do:
>
> while true
> do
> dd if=/dev/zero of=foo bs=1M count=512 conv=notrunc
> done
>
> and also:
>
> rm 1 ; sleep 3; time dd if=/dev/zero of=1 bs=16M count=1
>
> The 16M dd normally takes 1.5 seconds (I'm pretty please with that btw.
> Very repeatable and fair). If you run the 16M dd with SCHED_FIFO it takes
> a repeatable 0.12 seconds.
This is what I did. Same results, basically.
What I did not do was prove that the xmms stalls went away for those who
were seeing that.
> So running a program off disk isn't a very good test.
No, its not. And in general, real-time tasks should not do disk I/O (at
least not via their core RT thread). And they should mlock() their
memory.
But circumstances do differ, and these changes are in the right
direction, I think. It also means e.g. someone can make xmms or whatever
real-time, and hopefully avoid the memory-related stalls that spawned
the discussion and this patch.
Robert Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2003-08-06 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 22:13 Robert Love
2003-08-06 0:09 ` Andrew Morton
2003-08-06 0:39 ` Robert Love
2003-08-06 0:45 ` Andrew Morton
2003-08-06 3:58 ` Robert Love
2003-08-06 8:41 ` Andrew Morton
2003-08-06 17:01 ` Robert Love [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:
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=1060189274.4494.212.camel@localhost \
--to=rml@tech9.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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