[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1330388974-27793-1-git-send-email-john.stultz@linaro.org>
Date: Mon, 27 Feb 2012 16:29:27 -0800
From: John Stultz <john.stultz@...aro.org>
To: lkml <linux-kernel@...r.kernel.org>
Cc: John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Eric Dumazet <eric.dumazet@...il.com>,
Richard Cochran <richardcochran@...il.com>
Subject: [GIT PULL][PATCH 0/7] Reduce timekeeping lock hold time
Here is the second half of the timekeeping cleanups (the first
half are already in -tip) as well as some changes to reduce the
timekeeping lock hold times.
This work grew out of some of Eric Dumazet's and Thomas Gleixner's
suggestions, after they noticed the xtime_lock hold time could be
on the long side.
The basic idea is that we keep a shadow copy of the timekeeper
stucture, which can be updated while readers are accessing the
time. Then we only have to block readers as we switch to the
newly updated structure.
I've done some limited testing, but it would be good to get
this in -tip early, so we can be sure it gets enough testing
before 3.4 is released.
CC: Thomas Gleixner <tglx@...utronix.de>
CC: Eric Dumazet <eric.dumazet@...il.com>
CC: Richard Cochran <richardcochran@...il.com>
thanks
-john
Thomas,
These patches are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.4/time
John Stultz (7):
time: Condense timekeeper.xtime into xtime_sec
time: Rework timekeeping functions to take timekeeper ptr as argument
time: Split timekeeper lock into separate reader/writer locks
time: Update timekeeper structure using a local shadow
time: Shadow cycle_last in timekeeper structure
time: Reduce timekeeper read lock hold time
time: Convert the timekeeper's wlock to a raw_spin_lock
kernel/time/timekeeping.c | 414 ++++++++++++++++++++++++++-------------------
1 files changed, 243 insertions(+), 171 deletions(-)
--
1.7.3.2.146.gca209
--
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/
Powered by blists - more mailing lists