public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/clock: cleanup, remove wrap_{max|min}().
Date: Wed, 7 May 2014 15:38:23 +0200	[thread overview]
Message-ID: <20140507133823.GN30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <536A2143.5090106@cn.fujitsu.com>

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

On Wed, May 07, 2014 at 09:04:19PM +0900, Dongsheng Yang wrote:
> On 05/07/2014 09:55 PM, Peter Zijlstra wrote:
> >On Wed, May 07, 2014 at 08:48:58PM +0900, Dongsheng Yang wrote:
> >>I am not sure why we need the wrap_{max|min}() in kernel/sched/clock.c.
> >>But I checked the implementation of max() and min() in linux/kernel.h, I think
> >>we can reuse them here rather than introduce a new function named
> >>wrap_{max|min}().
> >wrap is a good hint there.. they're supposed to deal with the clock
> >wrapping. Of course 2^64 ns is a rather long time (~584 years in fact),
> >but that doesn't mean we shouldn't care.
> >
> >And no, min/max don't do the right thing.
> 
> IMMO,  max() in kernel.h is checking and returning the u64 with typeof() if
> we are passing a u64 parameter to max(). And I checked current callers of
> wrap_max(),
> they are all passing parameters of u64 type. So I think max/min works well
> at
> the place of wrap_max/min().
> 
> Maybe I am missing something here, please correct me if I understand it
> incorrectly.

Trivial test prog; you really should do these things yourself.

$ ./wrap
wrap_min: 18446744073709551615 wrap_max: 0
min:      0 max:      18446744073709551615


---
#include <stdint.h>
#include <stdio.h>

typedef uint64_t u64;
typedef int64_t  s64;

static inline u64 wrap_min(u64 x, u64 y)
{
        return (s64)(x - y) < 0 ? x : y;
}

static inline u64 wrap_max(u64 x, u64 y)
{
        return (s64)(x - y) > 0 ? x : y;
}

#define min(x, y) ({                            \
        typeof(x) _min1 = (x);                  \
        typeof(y) _min2 = (y);                  \
        (void) (&_min1 == &_min2);              \
        _min1 < _min2 ? _min1 : _min2; })

#define max(x, y) ({                            \
        typeof(x) _max1 = (x);                  \
        typeof(y) _max2 = (y);                  \
        (void) (&_max1 == &_max2);              \
        _max1 > _max2 ? _max1 : _max2; })

void main (void)
{
        u64 a = UINT64_MAX, b = a + 1;

        printf("wrap_min: %lu wrap_max: %lu\n", wrap_min(a, b), wrap_max(a,b));
        printf("min:      %lu max:      %lu\n", min(a, b), max(a,b));
}

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-05-07 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 11:48 [PATCH] sched/clock: cleanup, remove wrap_{max|min}() Dongsheng Yang
2014-05-07 12:55 ` Peter Zijlstra
2014-05-07 12:04   ` Dongsheng Yang
2014-05-07 13:38     ` Peter Zijlstra [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=20140507133823.GN30445@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=yangds.fnst@cn.fujitsu.com \
    /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