Date: Wed, 31 Jan 2007 18:22:07 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, johnstul@us.ibm.com,
       Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 09/23] clocksource: add block notifier
Message-ID: <20070131172207.GF4468@elte.hu>
References: <20070131033710.420168478@mvista.com> <20070131033805.815147778@mvista.com> <20070131101710.GB22377@elte.hu> <1170257152.9781.36.camel@imap.mvista.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1170257152.9781.36.camel@imap.mvista.com>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 896
Lines: 22


* Daniel Walker <dwalker@mvista.com> wrote:

> > secondly, CLOCKSOURCE_NOTIFY_REGISTER is only used by the core 
> > clocksource code and no register-notifier interface is exposed: this 
> > makes the whole thing an expensive NOP.
> 
> I don't know what you mean when you say "no register-notifier 
> interface is exposed" .. The timekeeping code doesn't use this 
> notification , but it really should. [...]

what i say is that there's no public interface exposed of this notifier
(and even if there was, there isnt any user of it) and there's only a
single notifier used internally: this means that this thing is an
expensive function call.

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/