public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Documentation: fix getdelays.c example -l option and segv
Date: Wed, 15 Aug 2007 16:50:41 +0530	[thread overview]
Message-ID: <46C2E189.7040504@linux.vnet.ibm.com> (raw)
In-Reply-To: <11201.1187165591@neuling.org>

<snip>

>> Is this really required? a sleep() in the code. Why do we do multiple
>> send_cmd()'s in the do loop? I'll test and get back.
> 
> I needed to send another command to receive more data.  Without the per
> loop send_cmd, I never got any more stats. 
> 
> Should we receive more data without the additional send_cmd?  I've been
> running with: 
>   ./getdelays -d -p 1 -l
> 

Interesting, we never used -l that way. We used -l to get data for all
exiting tasks

./getdelays -d -l

For the usage you've mentioned, I'd use

while :
do
	sleep 2
	./getdelays -p 1 -d
done

I guess your changes change getdelays and since there are other ways
to obtaining the same data, I'd remove the last bit of changes made
to send the TGID often to get data.

> Mikey
> 
> 


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2007-08-15 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  8:24 [PATCH] Documentation: fix getdelays.c example -l option and segv Michael Neuling
2007-08-10  8:33 ` Andrew Morton
2007-08-10  8:53   ` Michael Neuling
2007-08-15  7:02 ` Balbir Singh
2007-08-15  8:13   ` Michael Neuling
2007-08-15 11:20     ` Balbir Singh [this message]
2007-08-15 12:00       ` Michael Neuling
2007-08-15 12:08       ` [PATCH] Documentation: fix getdelays.c printf bug Michael Neuling
2007-08-15 13:15         ` Balbir Singh

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=46C2E189.7040504@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikey@neuling.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