All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mark manning" <mark.manning@fastermail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: nanosleep
Date: Tue, 09 Apr 2002 23:42:43 -0500	[thread overview]
Message-ID: <20020410044243.2916.qmail@fastermail.com> (raw)


thanx - how much of a difference should i expect - i know the syscall is asking for at least the required ammount but that the task switcher might not give me control back for a while after the requested delay but i was expecting to be a little closer to what i had asked for - this isnt critical of corse but i would like to know what to expect.


----- Original Message -----
From: "H. Peter Anvin" <hpa@zytor.com>
Date: Tue, 09 Apr 2002 21:17:03 -0700
To: mark manning <mark.manning@fastermail.com>
Subject: Re: nanosleep


> mark manning wrote:
> > doh - i think something is still wrong, i ask for 1000 ms and i get a second but if i do a 500 itteration loop asking for 1 ms i get 5 seconds.  i am also starting to distrust my elapsed time display which is using the gettimeofday syscall
> > 
> 
> It doesn't work that way.  Each call to nanosleep() gives you a 
> *MINIMUM* time to delay.  The kernel may decide to schedule you away and 
> pick your process up when it suits it.
> 
> 	-hpa
> 
> 
> 

-- 

_______________________________________________
Get your free email from http://www.fastermail.com

Powered by Outblaze

             reply	other threads:[~2002-04-10  4:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10  4:42 mark manning [this message]
2002-04-10  5:47 ` nanosleep H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10  5:57 nanosleep mark manning
2002-04-10  6:01 ` nanosleep Robert Love
2002-04-13 21:53   ` nanosleep andrew may
2002-04-14 20:37     ` nanosleep H. Peter Anvin
2002-04-10  4:41 nanosleep mark manning
2002-04-10  5:57 ` nanosleep Robert Love
2002-04-10  3:22 nanosleep mark manning
2002-04-09 23:24 nanosleep mark manning

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=20020410044243.2916.qmail@fastermail.com \
    --to=mark.manning@fastermail.com \
    --cc=linux-kernel@vger.kernel.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 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.