[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200907211154.42563.knikanth@suse.de>
Date: Tue, 21 Jul 2009 11:54:42 +0530
From: Nikanth Karthikesan <knikanth@...e.de>
To: balbir@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org,
Guillaume Chazarain <guichaz@...il.com>,
procps-feedback@...ts.sf.net, Albert Cahalan <albert@...rs.sf.net>
Subject: Re: [PATCH 1/3] taskstats-fork: Add a new taskstats command to get notification on fork/clone
On Tuesday 21 July 2009 11:31:14 Balbir Singh wrote:
> * Nikanth Karthikesan <knikanth@...e.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
--
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