All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH-STACK] Updates, timerstats, rtdm-timers
Date: Wed, 06 Jun 2007 17:08:22 +0200	[thread overview]
Message-ID: <4666CDE6.4030402@domain.hid> (raw)
In-Reply-To: <4666B879.7000907@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Jan Kiszka wrote:
>>>
>>>> Jan Kiszka wrote:
>>>> ...
>>>>
>>>>> fast-tsc-to-ns-v2.patch
>>>>>
>>>>>    [Rebased, improved rounding of least significant digit]
>>>> Rounding in the fast path for the sake of the last digit was silly.
>>>> Instead, I'm now addressing the ugly interval printing via
>>>> xnarch_precise_tsc_to_ns when converting the timer interval back into
>>>> nanos. -v3 incorporating this has just been uploaded.
>>>>
>>> After noticing yesterday that even unpatched Xenomai sometimes converts
>>> inaccurately when showing small timer intervals under /proc, I just got
>>> an idea how to address this beautification issue even better: -v4 now
>>> rounds up in the slow, precise tsc-to-ns path, see
>>>
>>> http://www.rts.uni-hannover.de/rtaddon/patches/xenomai/fast-tsc-to-ns-v4.patch
>> I am the one who decided of the rounding behaviour of llimd, RTAI
>> version had the same rounding policy as the one you propose, and I made
>> it for the following reasons:
>> - rouding towards 0 is the policy used by the C language, so doing this
>> for llimd made it consistent with what one expects from C code;
>> - values computed by llimd are used to program timers, and we prefer the
>> timer to be programmed for a too short value than for a too long value.
> 
> That's OK, I agree. In my patch for i386, this rounding is only relevant
> for display purposes. It's just to help me finding the expected period T
> of my task in /proc instead of T-1 sometimes. Beautification. All we
> need for other archs is xnarch_tsc_to_ns according to the old scheme.
> Will rework this.

Done, -v5 is online.

This is not yet incorporating any change to the generic llmulshft. I
haven't thought about nor tried our code on a 64 bit arch yet. Did you
check this already? I wonder, eg., if it makes sense to exploit 128 bit
with 64 bit shifts there or stick with 94/32 bit accuracy and related
conversion errors. Depending on this, the generic version might have to
be reconsidered.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 23:25 [Xenomai-core] [PATCH-STACK] Updates, timerstats, rtdm-timers Jan Kiszka
2007-06-05  8:31 ` Jan Kiszka
2007-06-05 22:28   ` Gilles Chanteperdrix
2007-06-06 10:30     ` Jan Kiszka
2007-06-06 12:47       ` Gilles Chanteperdrix
2007-06-06 12:59         ` Jan Kiszka
2007-06-06 13:21           ` Gilles Chanteperdrix
2007-06-06 13:31             ` Jan Kiszka
2007-06-06 18:23               ` Gilles Chanteperdrix
2007-06-06 18:46                 ` Jan Kiszka
2007-06-07 12:52                   ` Jan Kiszka
2007-06-07 13:02                     ` Gilles Chanteperdrix
2007-06-07 14:06                       ` Jan Kiszka
2007-06-07 14:24                         ` Gilles Chanteperdrix
2007-06-07 14:40                           ` Jan Kiszka
2007-06-07 14:54                             ` Gilles Chanteperdrix
2007-06-06 12:49   ` Jan Kiszka
2007-06-06 13:29     ` Gilles Chanteperdrix
2007-06-06 13:36       ` Jan Kiszka
2007-06-06 15:08         ` Jan Kiszka [this message]

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=4666CDE6.4030402@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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.