mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, johnstul@us.ibm.com, mingo@elte.hu,
	zippel@linux-m68k.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + clocksource-add-generic-sched_clock.patch added to -mm tree
Date: Sun, 08 Oct 2006 23:41:55 +0200	[thread overview]
Message-ID: <1160343715.5686.118.camel@localhost.localdomain> (raw)
In-Reply-To: <1160343221.3693.154.camel@c-67-180-230-165.hsd1.ca.comcast.net>

On Sun, 2006-10-08 at 14:33 -0700, Daniel Walker wrote:
> On Sun, 2006-10-08 at 23:21 +0200, Thomas Gleixner wrote:
> > On Sun, 2006-10-08 at 14:15 -0700, Daniel Walker wrote:
> > > On Sun, 2006-10-08 at 20:45 +0200, Thomas Gleixner wrote:
> > > 
> > > > > I'm not moving the kernel/timer.c clocksource user back into
> > > > > kernel/time/clocksource.c . That code completely belongs with the
> > > > > generic time of day changes. The code is directly coupled, and in fact
> > > > > it improves the timekeeping clock switching code to have it that way.
> > > > 
> > > > I don't see any reason, why it must be added to timer.c. You can achieve
> > > > the same result with calling the code outside, except that the compiler
> > > > might miss some inline optimization. The switch clock code is not a
> > > > hotpath and so it does not matter whether it is called here or there.
> > > 
> > > It wouldn't be as clean to integrate the two. The hotpath is improved
> > > (which is what I was referring too above.)
> > 
> > Sorry, where is which hotpath improved ?
> 
> The hotpath in update_wall_time() kernel/timer.c which involves clock
> switching.

And why the heck does this require to move _clocksource_ related code
including sysfs hackery into timer.c ? Your improvement works with
extern code as well.

	tglx



  reply	other threads:[~2006-10-08 21:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200610070153.k971ruEZ020872@shell0.pdx.osdl.net>
2006-10-08  9:55 ` Thomas Gleixner
2006-10-08 14:45   ` Daniel Walker
2006-10-08 14:51     ` Thomas Gleixner
2006-10-08 15:32       ` Daniel Walker
2006-10-08 15:46         ` Thomas Gleixner
2006-10-08 16:06           ` Daniel Walker
2006-10-08 16:19             ` Thomas Gleixner
2006-10-08 16:27               ` Daniel Walker
2006-10-08 16:54                 ` Thomas Gleixner
2006-10-08 17:26                   ` Daniel Walker
2006-10-08 18:45                     ` Thomas Gleixner
2006-10-08 21:15                       ` Daniel Walker
2006-10-08 21:21                         ` Thomas Gleixner
2006-10-08 21:33                           ` Daniel Walker
2006-10-08 21:41                             ` Thomas Gleixner [this message]
2006-10-08 22:08                               ` Daniel Walker
2006-10-08 22:35                                 ` Thomas Gleixner
2006-10-08 23:01                                   ` Daniel Walker
2006-10-09  8:09                                     ` Thomas Gleixner
2006-10-08 18:40   ` 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=1160343715.5686.118.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@osdl.org \
    --cc=dwalker@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®