linux-kernel - Re: [PATCH 4/4]: [SPARC64]: Add clocksource/clockevents support.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 9 Mar 2007 11:53:43 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	sparclinux@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 4/4]: [SPARC64]: Add clocksource/clockevents support.


* David Miller <davem@...emloft.net> wrote:

> >From 1171ef62b18d7eef093ecf961dd09b11339d53d9 Mon Sep 17 00:00:00 2001
> From: David S. Miller <davem@...set.davemloft.net>
> Date: Mon, 5 Mar 2007 15:28:37 -0800
> Subject: [PATCH] [SPARC64]: Add clocksource/clockevents support.
> 
> I'd like to thank John Stul and others for helping me along the way.
> 
> A lot of cleanups fell out of this.  For example, the get_compare() 
> tick_op was totally unused, so was deleted.  And the most often used 
> tick_op members were grouped together for cache-friendlyness.

cool stuff! It's really gratifying to see that you were able to two new 
major features on Sparc64 (CONFIG_NO_HZ and CONFIG_HIGH_RES_TIMERS) via:

>  7 files changed, 25 insertions(+), 172 deletions(-)
>  4 files changed, 238 insertions(+), 230 deletions(-)

so it's in fact a net removal of code! I think this really demonstrates 
the power of unified frameworks.

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