From: Thomas Gleixner <tglx@linutronix.de>
To: Tsutomu OWA <tsutomu.owa@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch 4/4] powerpc 2.6.21-rt1: reduce scheduling latency by changing tlb flush size
Date: Mon, 14 May 2007 08:51:46 +0200 [thread overview]
Message-ID: <1179125506.22481.297.camel@localhost.localdomain> (raw)
In-Reply-To: <yyiveev9afk.wl@toshiba.co.jp>
Tsutomu-san,
On Mon, 2007-05-14 at 15:38 +0900, Tsutomu OWA wrote:
> Oopps, Subject was wrong.... resending it. Sorry.
>
> To reduce scheduling latecy by changing tlb flush size to 1.
> Since tlb flush on Celleb is done by calling (an) expensive hypervisor call(s),
> it takes a long time to flush tlbs and causes scheduing latency.
>
> As I don't know how long it takes on other platforms, it would be better to
> enclose it within #ifdef CONFIG_PPC_CELLEB.
Yes, that might be appropriate. Can you add this and resend please ?
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Tsutomu OWA <tsutomu.owa@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 4/4] powerpc 2.6.21-rt1: reduce scheduling latency by changing tlb flush size
Date: Mon, 14 May 2007 08:51:46 +0200 [thread overview]
Message-ID: <1179125506.22481.297.camel@localhost.localdomain> (raw)
In-Reply-To: <yyiveev9afk.wl@toshiba.co.jp>
Tsutomu-san,
On Mon, 2007-05-14 at 15:38 +0900, Tsutomu OWA wrote:
> Oopps, Subject was wrong.... resending it. Sorry.
>
> To reduce scheduling latecy by changing tlb flush size to 1.
> Since tlb flush on Celleb is done by calling (an) expensive hypervisor call(s),
> it takes a long time to flush tlbs and causes scheduing latency.
>
> As I don't know how long it takes on other platforms, it would be better to
> enclose it within #ifdef CONFIG_PPC_CELLEB.
Yes, that might be appropriate. Can you add this and resend please ?
tglx
next prev parent reply other threads:[~2007-05-14 7:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 6:22 [patch 0/4] powerpc 2.6.21-rt1: fix build a breakage and some minor issues Tsutomu OWA
2007-05-14 6:26 ` [patch 1/4] powerpc 2.6.21-rt1: fix a build breakage by adding __raw_*_relax() macros Tsutomu OWA
2007-05-14 6:28 ` [patch 2/4] powerpc 2.6.21-rt1: convert spinlocks to raw ones for Celleb Tsutomu OWA
2007-05-14 6:29 ` [patch 3/4] powerpc 2.6.21-rt1: add a need_resched_delayed() check Tsutomu OWA
2007-05-14 6:30 ` [patch 0/4] powerpc 2.6.21-rt1: reduce scheduling latency by changing tlb flush size Tsutomu OWA
2007-05-14 6:38 ` [patch 4/4] " Tsutomu OWA
2007-05-14 6:51 ` Thomas Gleixner [this message]
2007-05-14 6:51 ` Thomas Gleixner
2007-05-14 7:28 ` Tsutomu OWA
2007-05-14 7:28 ` Tsutomu OWA
2007-05-14 14:40 ` Arnd Bergmann
2007-05-14 14:40 ` Arnd Bergmann
2007-05-15 4:12 ` Tsutomu OWA
2007-05-15 4:12 ` Tsutomu OWA
2007-05-15 7:34 ` Benjamin Herrenschmidt
2007-05-15 7:34 ` Benjamin Herrenschmidt
2007-05-15 6:27 ` Tsutomu OWA
2007-05-15 7:38 ` Benjamin Herrenschmidt
2007-05-15 7:38 ` Benjamin Herrenschmidt
2007-05-15 8:08 ` Tsutomu OWA
2007-05-15 8:08 ` Tsutomu OWA
2007-05-15 8:40 ` Benjamin Herrenschmidt
2007-05-15 8:40 ` Benjamin Herrenschmidt
2007-05-15 7:23 ` Benjamin Herrenschmidt
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=1179125506.22481.297.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=tsutomu.owa@toshiba.co.jp \
/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.