mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Korty <joe.korty@ccur.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] create /proc/timer-wheel-list
Date: Mon, 24 Nov 2008 14:11:43 -0500	[thread overview]
Message-ID: <20081124191143.GA24281@tsunami.ccur.com> (raw)
In-Reply-To: <20081123100424.GW30453@elte.hu>

On Sun, Nov 23, 2008 at 05:04:24AM -0500, Ingo Molnar wrote:
> 
> * Joe Korty <joe.korty@ccur.com> wrote:
> 
> > On Sat, Nov 22, 2008 at 12:34:23PM -0500, Alexey Dobriyan wrote:
> > > On Fri, Nov 21, 2008 at 05:11:13PM -0500, Joe Korty wrote:
> > > > Create /proc/timer_wheel_list.
> > > >
> > > > This does for the timer wheel what /proc/timer_list
> > > > does for hrtimers -- provide a way of displaying what
> > > > timers are running on what cpus, and their attributes.
> > >
> > > The fact that it's called a timer wheel is just an implementation detail
> > > unsuitable for permanent file.
> >
> > Agreed.  I'll come up with something else.  lrtimer_list is a good
> > candidate.
> 
> no - please include it in /proc/timer_list instead. It already lists
> clockevents and hrtimers - listing timer-list timers would be a
> natural extension of that facility.

struct tvec_base and TVR_MASK & family are all local
to kernel/timers.c rather than in some header file,
so parts of the display code would need to remain in
kernel/timers.c.  Seems ugly, but is of course do-able.

Also, I am not sure why we are lumping all sorts of
disparate things in one display file.  Did proc files
become expensive somewhere along the line?

(Just asking before I go down a path that everyone will
hate, once they see the result).

Regards,
Joe

  reply	other threads:[~2008-11-24 19:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 22:11 Joe Korty
2008-11-22 17:34 ` Alexey Dobriyan
2008-11-23  1:59   ` Joe Korty
2008-11-23 10:04     ` Ingo Molnar
2008-11-24 19:11       ` Joe Korty [this message]
2008-11-25 16:06 ` Michael Kerrisk
2008-11-25 18:57   ` [PATCH] Display active jiffie timers in /proc/timer_list Joe Korty
2008-11-25 21:36     ` Thomas Gleixner
2008-11-25 22:23       ` Joe Korty
2008-11-25 22:53         ` Thomas Gleixner
2008-11-26 16:48     ` [PATCH] Display active jiffie timers in /proc/timer_list, v2 Joe Korty
2008-11-26 17:07       ` Greg KH
2008-11-26 17:34         ` Joe Korty
2008-11-26 17:39           ` Greg KH
2008-11-26 21:06             ` [PATCH] ABI Documentation for /proc/timer_list Joe Korty
2008-11-28 21:37               ` Michael Kerrisk
2008-12-01 18:11                 ` [PATCH] ABI Documentation for /proc/timer_list, v2 Joe Korty
2008-12-05 17:12                   ` Randy Dunlap
2008-12-05 19:01                     ` Joe Korty

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=20081124191143.GA24281@tsunami.ccur.com \
    --to=joe.korty@ccur.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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