9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christoph Lohmann <20h@r-36.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Sleep-complexity
Date: Sun,  8 May 2005 14:03:23 +0200	[thread overview]
Message-ID: <20050508140323.14c96b22.20h@r-36.net> (raw)

Good day.

Just do be sure that there is no scientifc paper that describes the pro
of using for() in sleep(2), as an architecture decision:

% cat /n/sources/plan9/sys/src/cmd/sleep.c
#include <u.h>
#include <libc.h>

void
main(int argc, char *argv[])
{
	long secs;

	if(argc>1)
		for(secs = atol(argv[1]); secs > 0; secs--)
			sleep(1000);
	exits(0);
}

% cat /sys/src/cmd/sleep.c
#include <u.h>
#include <libc.h>

void
main(int argc, char *argv[])
{

	if(argc>1)
		sleep(atol(argv[1]) * 1000);

	exits(0);
}

% ls -l /386/bin/sleep /386/bin/_sleep
--rwxrwxr-x M 8 none sys 3409 May  8  13:43 /386/bin/_sleep
--rwxrwxr-x M 8 sys  sys 3390 Max  8  13:44 /386/bin/sleep

Is there any reason for the for()-loop?

Sincerely,

Christoph


             reply	other threads:[~2005-05-08 12:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 12:03 Christoph Lohmann [this message]
2005-05-08 12:51 ` Sergey Reva
2005-05-08 16:50   ` Russ Cox
2005-05-08 17:28     ` Dan Cross
2005-05-08 18:56       ` jmk
2005-05-08 19:21         ` Bruce Ellis
2005-05-08 20:54           ` Charles Forsyth
2005-05-08 21:06             ` Charles Forsyth
2005-05-08 22:40         ` Dan Cross
2005-05-08 22:59           ` geoff
2005-05-09  7:28             ` Richard Miller
2005-05-09 13:14             ` Brantley Coile
2005-05-09 16:45             ` Mike Haertel
2005-05-09 20:10               ` Bruce Ellis
2005-05-09 22:46                 ` Charles Forsyth
2005-05-09  7:41           ` David Tolpin
2005-05-08 21:12       ` Charles Forsyth
2005-05-09 13:29         ` Nigel Roles
2005-05-09 14:03           ` Charles Forsyth
2005-05-10 17:09         ` boyd, rounin
2005-05-10 17:15           ` jmk
2005-05-10 18:34             ` boyd, rounin
2005-05-10 18:39               ` rog
2005-05-10 19:27               ` Ronald G. Minnich
2005-05-10 21:02                 ` David Leimbach
2005-05-10 21:20                   ` Bruce Ellis

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=20050508140323.14c96b22.20h@r-36.net \
    --to=20h@r-36.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).