From: Balbir Singh <balbir@in.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
rdunlap@xenotime.net, jlan@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: taskstats accounting info
Date: Wed, 21 Mar 2007 09:29:14 +0530 [thread overview]
Message-ID: <4600AD92.7070205@in.ibm.com> (raw)
In-Reply-To: <20070319083512.908fc695.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Thu, 15 Mar 2007 11:06:55 -0800 Andrew Morton wrote:
>
>>> It's the most portable example, since it does not depend on libnl.
>> err, what is libnl?
>
> lib-netlink (as already answered, but I wrote this last week)
>
I was referring to the library at http://people.suug.ch/~tgr/libnl/
>> If there exists some real userspace infrastructure which utilises
>> taskstats, can we please get a referece to it into the kernel
>> Documentation? Perhaps in the TASKSTATS Kconfig entry, thanks.
>
>
> Balbir, I was working with getdelays.c when I initially wrote
> these questions. Here is a small patch for it. Hopefully you can
> use it when you find the updated version of it.
>
> ~Randy
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> 1. add usage() function
>
> 2. add unknown character in %c format (was only in %d, not useful):
>
> ./getdelays: invalid option -- h
> Unknown option '?' (63)
>
> instead of:
>
> ./getdelays: invalid option -- h
> Unknown option 63
>
> (or just remove that message)
>
> 3. -v does not use an optarg, so remove ':' in getopt string after 'v';
>
Thanks, these look good. I'll add them to my local copy.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
prev parent reply other threads:[~2007-03-21 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 12:12 taskstats accounting info Randy.Dunlap
2007-03-14 12:18 ` Balbir Singh
2007-03-15 19:06 ` Andrew Morton
2007-03-15 22:37 ` Balbir Singh
2007-03-19 15:35 ` Randy Dunlap
2007-03-21 3:59 ` Balbir Singh [this message]
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=4600AD92.7070205@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rdunlap@xenotime.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.