[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090831052629.GA16742@balbir.in.ibm.com>
Date: Mon, 31 Aug 2009 10:56:29 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Guillaume Chazarain <guichaz@...il.com>
Cc: Nikanth Karthikesan <knikanth@...e.de>,
linux-kernel@...r.kernel.org, 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
* Guillaume Chazarain <guichaz@...il.com> [2009-08-30 21:52:22]:
> On Tue, Jul 21, 2009 at 8:24 AM, Nikanth Karthikesan<knikanth@...e.de> wrote:
> > Ah.. proc-events was the exact thing, I was looking for! Thanks.
>
> AFAICT proc-events can only be used by root, so that makes it
> unsuitable for *top.
>
> Anyway, iotop will always have to iterate over all threads to query
> their taskstats and other attributes, so the O(nr_threads) complexity
> is unavoidable.
>
Unless you want the stats for tgid in signal struct. In some cases we
accumulate, in some we don't. But yes irrespective or kernel/user
space the complexity exists.
--
Balbir
--
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