All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roel Kluin <12o3l@tiscali.nl>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 9/9] RT: Only dirty a cacheline if the priority is actually changing
Date: Sat, 20 Oct 2007 04:48:59 +0200	[thread overview]
Message-ID: <47196C9B.7090909@tiscali.nl> (raw)
In-Reply-To: <20071017185113.11272.50568.stgit@novell1.haskins.net>

Gregory Haskins wrote:
> We can avoid dirtying a rq related cacheline with a simple check, so why not.
> 
> Signed-off-by: Gregory Haskins <ghaskins@novell.com>
> ---
> 
>  0 files changed, 0 insertions(+), 0 deletions(-)

I think you wanted a patch here?

  reply	other threads:[~2007-10-20  2:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 18:50 [PATCH 0/9] RT: RT-Overload/Sched enhancements v4 Gregory Haskins
2007-10-17 18:50 ` [PATCH 1/9] RT: push-rt Gregory Haskins
2007-10-17 18:50 ` [PATCH 2/9] RT: Add a per-cpu rt_overload indication Gregory Haskins
2007-10-17 18:50 ` [PATCH 3/9] RT: Wrap the RQ notion of priority to make it conditional Gregory Haskins
2007-10-17 18:50 ` [PATCH 4/9] RT: Initialize the priority value Gregory Haskins
2007-10-17 18:50 ` [PATCH 5/9] RT: Maintain the highest RQ priority Gregory Haskins
2007-10-17 18:50 ` [PATCH 6/9] RT: Clean up some of the push-rt logic Gregory Haskins
2007-10-17 18:51 ` [PATCH 7/9] RT: Add support for low-priority wake-up to push_rt feature Gregory Haskins
2007-10-17 18:51 ` [PATCH 8/9] RT: Fixes for push-rt patch Gregory Haskins
2007-10-18 11:00   ` Javier Sanz
2007-10-17 18:51 ` [PATCH 9/9] RT: Only dirty a cacheline if the priority is actually changing Gregory Haskins
2007-10-20  2:48   ` Roel Kluin [this message]
2007-10-20  7:54     ` Steven Rostedt
2007-10-20 10:44     ` Gregory Haskins

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=47196C9B.7090909@tiscali.nl \
    --to=12o3l@tiscali.nl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /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.