aboutsummaryrefslogtreecommitdiff
path: root/mm/mlock.c
diff options
context:
space:
mode:
authorjohn stultz <johnstul@us.ibm.com>2009-02-18 16:02:22 -0800
committerIngo Molnar <mingo@elte.hu>2009-02-19 10:10:08 +0100
commitfdcedf7b75808dd72c3cc0b931be11b04d75c60a (patch)
treec64743890ffa9722f8705ce0c214f0f08ffe4d9a /mm/mlock.c
parentba95fd47d177d46743ad94055908d22840370e06 (diff)
time: apply NTP frequency/tick changes immediately
Since the GENERIC_TIME changes landed, the adjtimex behavior changed for struct timex.tick and .freq changed. When the tick or freq value is set, we adjust the tick_length_base in ntp_update_frequency(). However, this new value doesn't get applied to tick_length until the next second (via second_overflow). This means some applications that do quick time tweaking do not see the requested change made as quickly as expected. I've run a few tests with this change, and ntpd still functions fine. Signed-off-by: John Stultz <johnstul@us.ibm.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'mm/mlock.c')
0 files changed, 0 insertions, 0 deletions