mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@redhat.com>
Subject: [RFC PATCH 0/3] posix_cpu_timers: Some code consolidation
Date: Tue,  5 Mar 2013 15:01:19 +0100	[thread overview]
Message-ID: <1362492082-23019-1-git-send-email-fweisbec@gmail.com> (raw)

Hi,

Some interesting consolidation comes when we unify the expiry
time type.

I'm also wondering: can't we implement CPUCLOCK_PROF using CPUCLOCK_SCHED?
One is using the tick, the other is using the sched. But they both seem
to account the same thing: utime + stime.

Thanks.

Frederic Weisbecker (3):
  posix_cpu_timers: Consolidate expiry time type
  posix_cpu_timers: Consolidate timer list cleanups
  posix_cpu_timers: Consolidate expired timers check

 include/linux/posix-timers.h |   16 ++-
 kernel/posix-cpu-timers.c    |  387 +++++++++++++++---------------------------
 2 files changed, 146 insertions(+), 257 deletions(-)

-- 
1.7.5.4


             reply	other threads:[~2013-03-05 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 14:01 Frederic Weisbecker [this message]
2013-03-05 14:01 ` [PATCH 1/3] posix_cpu_timer: Consolidate expiry time type Frederic Weisbecker
2013-03-05 14:01 ` [PATCH 2/3] posix_cpu_timers: Consolidate timer list cleanups Frederic Weisbecker
2013-03-05 14:01 ` [PATCH 3/3] posix_cpu_timers: Consolidate expired timers check Frederic Weisbecker

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=1362492082-23019-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=sgruszka@redhat.com \
    --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
Powered by JetHome