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: 05 Aug 2003 20:58:11 -0700 [thread overview]
Message-ID: <1060142290.4494.197.camel@localhost> (raw)
In-Reply-To: <20030805174536.6cb5fbf0.akpm@osdl.org>
On Tue, 2003-08-05 at 17:45, Andrew Morton wrote:
> It's testing time.
Just via some instrumenting, I can see that a real-time task never
begins throttling and this translates to a ~1ms reduction in worst case
allocation on a fast machine latency under extreme page dirtying and
writeback (basically, I cannot reproduce any variation in page
allocation, now, for a real-time test app). So it works.
But I do not have any real world test to confirm a benefit, which is
what matters. Have you poked and prodded?
Robert Love
WARNING: multiple messages have this Message-ID (diff)
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: 05 Aug 2003 20:58:11 -0700 [thread overview]
Message-ID: <1060142290.4494.197.camel@localhost> (raw)
In-Reply-To: <20030805174536.6cb5fbf0.akpm@osdl.org>
On Tue, 2003-08-05 at 17:45, Andrew Morton wrote:
> It's testing time.
Just via some instrumenting, I can see that a real-time task never
begins throttling and this translates to a ~1ms reduction in worst case
allocation on a fast machine latency under extreme page dirtying and
writeback (basically, I cannot reproduce any variation in page
allocation, now, for a real-time test app). So it works.
But I do not have any real world test to confirm a benefit, which is
what matters. Have you poked and prodded?
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>
next prev parent reply other threads:[~2003-08-06 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 22:13 [patch] real-time enhanced page allocator and throttling Robert Love
2003-08-05 22:13 ` Robert Love
2003-08-06 0:09 ` Andrew Morton
2003-08-06 0:09 ` Andrew Morton
2003-08-06 0:39 ` Robert Love
2003-08-06 0:39 ` Robert Love
2003-08-06 0:45 ` Andrew Morton
2003-08-06 0:45 ` Andrew Morton
2003-08-06 3:58 ` Robert Love [this message]
2003-08-06 3:58 ` Robert Love
2003-08-06 8:41 ` Andrew Morton
2003-08-06 8:41 ` Andrew Morton
2003-08-06 17:01 ` Robert Love
2003-08-06 17:01 ` Robert Love
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=1060142290.4494.197.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.