mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Divyesh Shah <dpshah@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, kenchen@google.com
Subject: Re: [PATCH][RESEND] Export per-tid and per-tgid cputime in  nanoseconds.
Date: Mon, 1 Mar 2010 07:44:04 -0800	[thread overview]
Message-ID: <af41c7c41003010744m54fc325bjccae0ff6965656eb@mail.gmail.com> (raw)
In-Reply-To: <1267271025.22519.740.camel@laptop>

On Sat, Feb 27, 2010 at 3:43 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Fri, 2010-02-26 at 18:03 -0800, Divyesh Shah wrote:
> > This can be used by applications to get finer granularity cputime usage on
> > platforms that use timestamp counters or HPET.
>
> I guess the patch looks good, I'm just not sure what HPET got to do with
> anything.. the scheduler certainly doesn't use HPET for timekeeping, its
> terribly slow to read.

Yes you're right. Please ignore the HPET comment.

>
> Also, it would be good to get some more justification than 'some
> applications can use this', which is basically a truism for any patch
> that adds a user interface.

1) This should be useful for a shared or virtualized environment where
the shared management infrastructure needs to charge each application
as accurately as possible for cpu usage.
2) An application that services different users and does some
cpu-intensive work may want to measure cpu time spent for each user by
the serving thread.

I think applications like web servers, remote database servers, etc.
fit into the second category.

For units of work smaller than a jiffy, this really helps as some
threads could potentially hide from the jiffy based accounting.

Please let me know if you want me to send the patch again with the
corrected description and added justification.

>
> > Signed-off-by: Divyesh Shah<dpshah@google.com>
> > ---
> >
> >  fs/proc/array.c    |   40 ++++++++++++++++++++++++++++++++++++++++
> >  fs/proc/base.c     |    2 ++
> >  fs/proc/internal.h |    2 ++
> >  3 files changed, 44 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/proc/array.c b/fs/proc/array.c
> > index 13b5d07..54604b8 100644
> > --- a/fs/proc/array.c
> > +++ b/fs/proc/array.c
> > @@ -547,3 +547,43 @@ int proc_pid_statm(struct seq_file *m, struct pid_namespace *ns,
> >
> >       return 0;
> >  }
> > +
> > +static int do_task_cputime(struct task_struct *task, char * buffer, int whole)
> > +{
> > +     int res;
> > +     unsigned long flags;
> > +     unsigned long long sum_exec_runtime = 0;
> > +     struct task_struct *t;
> > +
> > +     if (lock_task_sighand(task, &flags)) {
> > +             if (whole) {
> > +                     t = task;
> > +                     /*
> > +                      * Add up live thread sum_exec_runtime at the group
> > +                      * level.
> > +                      */
> > +                     do {
> > +                             sum_exec_runtime += t->se.sum_exec_runtime;
> > +                             t = next_thread(t);
> > +                     } while (t != task);
> > +                     sum_exec_runtime += task->signal->sum_sched_runtime;
> > +             }
> > +             unlock_task_sighand(task, &flags);
> > +     }
> > +
> > +     if (!whole)
> > +             sum_exec_runtime = task->se.sum_exec_runtime;
> > +
> > +     res = sprintf(buffer,"%llu\n", sum_exec_runtime);
> > +     return res;
> > +}
> > +
> > +int proc_tid_cputime(struct task_struct *task, char * buffer)
> > +{
> > +     return do_task_cputime(task, buffer, 0);
> > +}
> > +
> > +int proc_tgid_cputime(struct task_struct *task, char * buffer)
> > +{
> > +     return do_task_cputime(task, buffer, 1);
> > +}
> > diff --git a/fs/proc/base.c b/fs/proc/base.c
> > index 58324c2..8fbc785 100644
> > --- a/fs/proc/base.c
> > +++ b/fs/proc/base.c
> > @@ -2595,6 +2595,7 @@ static const struct pid_entry tgid_base_stuff[] = {
> >       REG("numa_maps",  S_IRUGO, proc_numa_maps_operations),
> >  #endif
> >       REG("mem",        S_IRUSR|S_IWUSR, proc_mem_operations),
> > +     INF("cputime_ns", S_IRUGO, proc_tgid_cputime),
> >       LNK("cwd",        proc_cwd_link),
> >       LNK("root",       proc_root_link),
> >       LNK("exe",        proc_exe_link),
> > @@ -2930,6 +2931,7 @@ static const struct pid_entry tid_base_stuff[] = {
> >       REG("numa_maps", S_IRUGO, proc_numa_maps_operations),
> >  #endif
> >       REG("mem",       S_IRUSR|S_IWUSR, proc_mem_operations),
> > +     INF("cputime_ns", S_IRUGO, proc_tid_cputime),
> >       LNK("cwd",       proc_cwd_link),
> >       LNK("root",      proc_root_link),
> >       LNK("exe",       proc_exe_link),
> > diff --git a/fs/proc/internal.h b/fs/proc/internal.h
> > index 1f24a3e..f9e9799 100644
> > --- a/fs/proc/internal.h
> > +++ b/fs/proc/internal.h
> > @@ -51,6 +51,8 @@ extern int proc_pid_status(struct seq_file *m, struct pid_namespace *ns,
> >                               struct pid *pid, struct task_struct *task);
> >  extern int proc_pid_statm(struct seq_file *m, struct pid_namespace *ns,
> >                               struct pid *pid, struct task_struct *task);
> > +extern int proc_tid_cputime(struct task_struct *, char *);
> > +extern int proc_tgid_cputime(struct task_struct *, char *);
> >  extern loff_t mem_lseek(struct file *file, loff_t offset, int orig);
> >
> >  extern const struct file_operations proc_maps_operations;
> >
>
>

  reply	other threads:[~2010-03-01 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  2:03 Divyesh Shah
2010-02-27 11:43 ` Peter Zijlstra
2010-03-01 15:44   ` Divyesh Shah [this message]
2010-03-01 18:05     ` Peter Zijlstra
2010-03-22 18:57       ` Divyesh Shah

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=af41c7c41003010744m54fc325bjccae0ff6965656eb@mail.gmail.com \
    --to=dpshah@google.com \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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

all inboxes | Powered by JetHome®