From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753994AbbCaBIN (ORCPT ); Mon, 30 Mar 2015 21:08:13 -0400 Received: from mail1.vodafone.ie ([213.233.128.43]:17237 "EHLO mail1.vodafone.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752066AbbCaBIJ (ORCPT ); Mon, 30 Mar 2015 21:08:09 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvUKAMzyGVVtT9Bt/2dsb2JhbABcgwaBLoMTyCwCgT5MAQEBAQEBfUEBg1MBBSMPAUYQCw0LAgIFFA0CAg8CRgYBDAEFAgEBiC8BsyKFaZMsAQEBAQYBAQEBAR2BIYoIhHgHgmiBRQWbbIYBC4lFg0gig289MYJDAQEB Message-ID: <5519F376.30105@draigBrady.com> Date: Tue, 31 Mar 2015 02:08:06 +0100 From: =?UTF-8?B?UMOhZHJhaWcgQnJhZHk=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Namhyung Kim , Steven Rostedt CC: Shuah Khan , LKML , Michael Ellerman , Dave Jones , Luis Henriques Subject: Re: [PATCH] ftracetest: Do not use usleep References: <1427329943-16896-1-git-send-email-namhyung@kernel.org> <20150330171511.5722493b@gandalf.local.home> <20150331004855.GF32033@sejong> In-Reply-To: <20150331004855.GF32033@sejong> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 31/03/15 01:48, Namhyung Kim wrote: > Hi Steve, > > On Mon, Mar 30, 2015 at 05:15:11PM -0400, Steven Rostedt wrote: >> On Thu, 26 Mar 2015 09:32:23 +0900 >> Namhyung Kim wrote: >> >>> The usleep is only provided on distros from Redhat so running ftracetest >>> on other distro resulted in failures due to the missing usleep. >>> >>> The reason of using [u]sleep in the test was to generate (scheduler) >>> events. But as we use 'cat trace | grep | wc -l' to read the events, >>> the command themselves already generate some events before reading the >>> trace file so no need to call [u]sleep explicitly. >> >> Note, opening "trace" via cat stops tracing. There is a possible race >> where the cat will not produce events. My worry is that if the shell >> implements its own "cat" command, it may not fork, and open the trace >> file. Which would not have any events in it, and opening it will >> disable the rest of the command from having events. > > I understand your point. But this is not just cat, it needs grep and > wc also. So I think there should be scheduler event(s). > >> >> What about using: >> >> ping localhost -c 1 >> >> ? > > I'm okay with ping though but worried if some tiny system might lack > the ping command.. I'd use a fallback method like: yield() { sleep .001 || usleep 1 || sleep 1; } Then just s/usleep 1/yield/ cheers, Pádraig.