From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Timekeeping changes for 3.4
Date: Wed, 01 Feb 2012 19:02:44 -0800 [thread overview]
Message-ID: <1328151764.2342.118.camel@work-vm> (raw)
Hey Thomas,
Here's the first chunk of my big timekeeping change queue, for 3.4.
Most of it should be fairly straight forward cleanups, moving values
into the timekeeper structure and changing the locking away from
xtime_lock.
Again, since tip/timers/core hasn't been updated since 3.3 was out,
these are against Linus' head (actually, from a week or so ago). Let me
know if you'd like me to base them off of something else.
Also, the more aggressive changes that will allow for reduced lock hold
times, which I'm holding off for 3.5 or later, can be found here if you
want to take a look at them, or possibly merge them earlier into a
3.4-rt tree for extra testing:
http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=shortlog;h=refs/heads/dev/xtime-breakup
thanks
-john
The patches are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.4/time
John Stultz (10):
time: Move total_sleep_time into the timekeeper structure
time: Move wall_to_monotonic into the timekeeper structure
time: Move xtime into timekeeeper structure
time: Move raw_time into timekeeper structure
time: Cleanup global variables and move them to the top
time: Add timekeeper lock
ntp: Cleanup timex.h
ntp: Access tick_length variable via ntp_tick_length()
ntp: Add ntp_lock to replace xtime_locking
time: Remove most of xtime_lock usage in timekeeping.c
Thomas Gleixner (2):
time: Reorder so the hot data is together
time: Move common updates to a function
include/linux/timex.h | 17 +--
kernel/time/ntp.c | 83 +++++++++---
kernel/time/timekeeping.c | 338 ++++++++++++++++++++++++--------------------
3 files changed, 248 insertions(+), 190 deletions(-)
reply other threads:[~2012-02-02 3:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1328151764.2342.118.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).