All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, "Jack O'Quin" <joq@io.com>
Subject: Re: Latency tests with 2.6.12-rc1
Date: Sat, 19 Mar 2005 02:51:42 -0500	[thread overview]
Message-ID: <1111218702.13039.5.camel@mindpipe> (raw)
In-Reply-To: <20050319070810.GA20059@elte.hu>

On Sat, 2005-03-19 at 08:08 +0100, Ingo Molnar wrote:
> great! The change in question is most likely the copy_page_range() fix
> that Hugh resurrected:
> 
> ChangeSet 1.2037, 2005/03/08 09:26:46-08:00, hugh@veritas.com
> 
> 	[PATCH] copy_pte_range latency fix
> 	
> 	Ingo's patch to reduce scheduling latencies, by checking for lockbreak in
> 	copy_page_range, was in the -VP and -mm patchsets some months ago; but got
> 	preempted by the 4level rework, and not reinstated since. Restore it now
> 	in copy_pte_range - which mercifully makes it easier.
> 
> are the ext3 related latencies are gone as well - or are you working it
> around by not using data=ordered?

As a matter of fact the ext3 latencies do not appear to be causing
problems, at least not at those settings, even with data=ordered.

It's impossible to tell much more because the mainline kernel lacks the
instrumentation that the realtime patchset provides.

Lee




  reply	other threads:[~2005-03-19  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19  4:03 Latency tests with 2.6.12-rc1 Lee Revell
2005-03-19  7:08 ` Ingo Molnar
2005-03-19  7:51   ` Lee Revell [this message]
2005-03-19 21:56     ` Lee Revell
2005-03-22  8:22       ` Ingo Molnar
2005-03-23 22:12         ` Lee Revell
2005-03-24 17:13           ` Lee Revell
2005-03-31  8:02       ` Ingo Molnar

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=1111218702.13039.5.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=joq@io.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.