All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikanth Karthikesan <knikanth@suse.de>
To: balbir@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org,
	Guillaume Chazarain <guichaz@gmail.com>,
	procps-feedback@lists.sf.net,
	Albert Cahalan <albert@users.sf.net>
Subject: Re: [PATCH 1/3] taskstats-fork: Add a new taskstats command to get notification on fork/clone
Date: Tue, 21 Jul 2009 11:54:42 +0530	[thread overview]
Message-ID: <200907211154.42563.knikanth@suse.de> (raw)
In-Reply-To: <20090721060114.GS24157@balbir.in.ibm.com>

On Tuesday 21 July 2009 11:31:14 Balbir Singh wrote:
> * Nikanth Karthikesan <knikanth@suse.de> [2009-07-21 10:31:48]:
> > Add a new taskstats command to register for notification, whenever a new
> > task forks in the cpumask specified.
>
> The changelog is sucky.. why do we need this? Why is proc-events not
> sufficient?

Ah.. proc-events was the exact thing, I was looking for! Thanks. But it seems 
there is no documentation for it? May be I didn't search properly...

BTW I did mention the need for this, in 
http://patchwork.kernel.org/patch/36451/ , but didn't invest time to write a 
good changelog here, as I suspected something exists already. Sorry. ;-(

[CC-ed iotop/top people, who were CC-ed in the above mail. So that they can 
consider using proc-events interface, if it was not considered/used already]

Thanks
Nikanth

  reply	other threads:[~2009-07-21  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21  5:01 [PATCH 1/3] taskstats-fork: Add a new taskstats command to get notification on fork/clone Nikanth Karthikesan
2009-07-21  6:01 ` Balbir Singh
2009-07-21  6:24   ` Nikanth Karthikesan [this message]
2009-08-30 19:52     ` Guillaume Chazarain
2009-08-31  5:26       ` Balbir Singh
2009-08-31  9:11       ` Nikanth Karthikesan

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=200907211154.42563.knikanth@suse.de \
    --to=knikanth@suse.de \
    --cc=albert@users.sf.net \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=guichaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=procps-feedback@lists.sf.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.