[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100127171335.7edf041d.akpm@linux-foundation.org>
Date: Wed, 27 Jan 2010 17:13:35 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jiri Slaby <jslaby@...e.cz>
Cc: mingo@...e.hu, linux-kernel@...r.kernel.org, jirislaby@...il.com,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/2] core: posix-cpu-timers, cleanup rlimits usage
On Wed, 27 Jan 2010 17:34:30 +0100
Jiri Slaby <jslaby@...e.cz> wrote:
> Fetch rlimit (both hard and soft) values only once and work on them.
> It removes many accesses through sig structure and makes the code
> cleaner.
The patch doesn't apply for me in semi-serious ways because I applied
rather a lot of timer-related patches:
timer-stats-fix-del_timer_sync-and-try_to_del_timer_sync.patch
posix-cpu-timers-reset-expire-cache-when-no-timer-is-running.patch
hrtimer-correct-a-few-numbers-in-comments.patch
clockevents-ensure-taht-min_delta_ns-is-increased-in-error-path.patch
clocksource-add-argument-to-resume-callback.patch
clocksource-start-cmt-at-clocksource-resume.patch
clocksource-add-suspend-callback.patch
posix-timersc-dont-export-local-functions.patch
timers-introduce-the-concept-of-timer-slack-for-legacy-timers.patch
cpu-timers-simplify-rlimit_cpu-handling.patch
cpu-timers-cleanup-arm_timer.patch
cpu-timers-return-correct-previous-timer-reload-value.patch
cpu-timers-change-sigev_none-timer-implementation.patch
cpu-timers-assure-to-not-iterate-over-all-threads-in-fastpath_timer_check.patch
cpu-timers-optimize-run_posix_cpu_timers.patch
(The above patches are up to six months old. Something isn't working right).
--
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