public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Woodruff, Richard" <r-woodruff2@ti.com>,
	"linux-arm-kernel@lists.arm.linux.org.uk"
	<linux-arm-kernel@lists.arm.linux.org.uk>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Paul Walmsley <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 5/6] ARM: OMAP2: drop redundant pending write check for gptimer
Date: Sun, 7 Dec 2008 12:54:29 -0800	[thread overview]
Message-ID: <20081207205428.GA7388@atomide.com> (raw)
In-Reply-To: <20081207170624.GA17640@flint.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [081207 09:06]:
> On Sun, Dec 07, 2008 at 08:55:54AM -0600, Woodruff, Richard wrote:
> > Yes, NOHZ is _poor_ today in respect to needless reprogramming. Code can
> > be improved. I have sent Thomas a patch for the same which is in the MM
> > tree for a while now.
> 
> When I discussed this problem with Thomas, his reaction was rather
> negative due to there being conflicting requirements between this and
> ia64.  And quite frankly I think that the OMAP behaviour is utter
> madness - taking as long as it does to update the timer registers
> means that no matter what you do, you _will_ be paying a penalty
> for that hardware.

Well still the timer code should be optimized for slower systems.
The timer should not be reprogrammed during every device interrupt
if the change is less than a jiffy. And going through the
timer lists is not always needed, so Richard's patch tries to
optimize that [1].

> Let's hope that later OMAP designs sanitise the timer hardware so
> it doesn't take stupid amounts of time to write to the registers,
> posted mode or not.

Yeah. Richard has some profiling data showing you how much time is
spent doing that, maybe post that again for reference? It's very
interesting data.

Tony


[1] http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.28-rc2/2.6.28-rc2-mm1/broken-out/tick-schedc-suppress-needless-timer-reprogramming.patch

  reply	other threads:[~2008-12-07 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05  2:38 [PATCH 0/6] Omap2 updates for 2.6.29 merge window Tony Lindgren
2008-12-05  2:39 ` [PATCH 1/6] ARM: OMAP2: Prepare cpu detection for further improvements Tony Lindgren
2008-12-05  2:39 ` [PATCH 2/6] ARM: OMAP2: Fix cpu detection Tony Lindgren
2008-12-05  2:40 ` [PATCH 3/6] ARM: OMAP2: Use omap_rev() instead of system_rev Tony Lindgren
2008-12-05  2:40 ` [PATCH 4/6] ARM: OMAP2: bard-h4: list those eeproms Tony Lindgren
2008-12-05  2:41 ` [PATCH 5/6] ARM: OMAP2: drop redundant pending write check for gptimer Tony Lindgren
2008-12-07 11:25   ` Russell King - ARM Linux
2008-12-07 14:55     ` Woodruff, Richard
2008-12-07 17:06       ` Russell King - ARM Linux
2008-12-07 20:54         ` Tony Lindgren [this message]
2008-12-11 22:14         ` Paul Walmsley
2008-12-05  2:41 ` [PATCH 6/6] ARM: OMAP2: skip unnecessary TLDR write during non-autoreload " Tony Lindgren

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=20081207205428.GA7388@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox