From: Ingo Molnar <mingo@elte.hu>
To: Lee Revell <rlrevell@joe-job.com>
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 08:08:10 +0100 [thread overview]
Message-ID: <20050319070810.GA20059@elte.hu> (raw)
In-Reply-To: <1111204984.12740.22.camel@mindpipe>
* Lee Revell <rlrevell@joe-job.com> wrote:
> I did the same quick latency tests with 2.6.12-rc1 that I posted about
> for 2.6.11 a few weeks ago.
>
> 2.6.12-rc1 is significantly better than 2.6.11. Running JACK at 64
> frames (1.3 ms) works very well. I was not able to produce xruns even
> with "dbench 64", which slows the system to a crawl. With 2.6.11, I
> could easily produce xruns with much lighter loads.
>
> It would appear that the latency issues related to the 4 level page
> tables merge have been resolved.
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?
Ingo
next prev parent reply other threads:[~2005-03-19 7:09 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 [this message]
2005-03-19 7:51 ` Lee Revell
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=20050319070810.GA20059@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=joq@io.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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.