diff for duplicates of <20090107133230.GA28694@sgi.com> diff --git a/a/content_digest b/N1/content_digest index 2d554f7..f59a24f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,7 +10,7 @@ "ref\01231322037.11687.178.camel@twins\0" "From\0Dimitri Sivanich <sivanich@sgi.com>\0" "Subject\0Re: [PATCH] configure HAVE_UNSTABLE_SCHED_CLOCK for SGI_SN systems\0" - "Date\0Wed, 07 Jan 2009 13:32:30 +0000\0" + "Date\0Wed, 7 Jan 2009 07:32:30 -0600\0" "To\0Peter Zijlstra <peterz@infradead.org>\0" "Cc\0Robin Holt <holt@sgi.com>" Nick Piggin <npiggin@suse.de> @@ -31,4 +31,4 @@ "\n" Admittedly I have not looked at this possibility too closely, but my initial concern upon looking at sched_clock_cpu() for the UNSTABLE case was the lock_double_clock() and what sort of contention that might cause on larger systems under certain conditions. -2d8683b1d1985e40607679e0d6ed0073ffbd423d354a0df8bf54aea11a70baac +4ebab2e63198d792ca4c809728635e50e1b46a82fb43da26b0025ad7aaac463f
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.