public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Riley Williams <Riley@Williams.Name>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, Eric Piel <Eric.Piel@Bull.Net>
Subject: Re: [PATCH] More time clean up stuff.
Date: Tue, 10 Jun 2003 08:40:24 -0700	[thread overview]
Message-ID: <3EE5FBE8.7020900@mvista.com> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAEEEGEEAA.Riley@Williams.Name>

Riley Williams wrote:
> Hi George.
> 
> I'm ignoring the rest of this - it makes sense to me, but I'm
> no expert in it. However, your last point is one I can comment
> about as I've dealt with it professionally many times.
> 
>  > clock_nanosleep is changed to round up to the next jiffie to
>  > cover starting between jiffies.
> 
> Isn't this a case of replacing one error with another, where
> one of the two errors is unavoidable?
> 
>  1. In the old case, the sleep will on average be half a jiffie
>     LESS than the requested period.
> 
>  2. In the new case, the sleep will on average be half a jiffie
>     MORE than the requested period.
> 
> One or the other is unavoidable if a jiffie is the basic unit
> of time resolution of the system. However, the error is totally
> meaningless if we are asking to sleep for more than 15 jiffies.

I had a hard time justifiying this also.  I would really like to have 
better resolution.  As to which choice to make, the standard is VERY 
clear here:  No timer or sleep shall complete BEFORE its time.
> 
> Best wishes from Riley.
> ---
>  * Nothing as pretty as a smile, nothing as ugly as a frown.
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.488 / Virus Database: 287 - Release Date: 5-Jun-2003
> 
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2003-06-10 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10  0:57 [PATCH] More time clean up stuff george anzinger
2003-06-10  8:18 ` Riley Williams
2003-06-10 11:52   ` Eric Piel
2003-06-10 15:40   ` george anzinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:54 george anzinger

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=3EE5FBE8.7020900@mvista.com \
    --to=george@mvista.com \
    --cc=Eric.Piel@Bull.Net \
    --cc=Riley@Williams.Name \
    --cc=akpm@digeo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox