public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: backwards busy wait using "time_before()"??
Date: Thu, 31 Dec 2009 14:23:02 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912311421290.5803@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0912311136560.3596@localhost>

On Thu, 31 Dec 2009, Robert P. J. Day wrote:

>
>   if this is an idiotic question, i'll blame it on the fact that
> there's only decaf left in the house.
>
>   from drivers/spi/spi_stmp.c:
>
>    #define busy_wait(cond)                                              \
>         ({                                                              \
>         unsigned long end_jiffies = jiffies + STMP_SPI_TIMEOUT;         \
>         bool succeeded = false;                                         \
>         do {                                                            \
>                 if (cond) {                                             \
>                         succeeded = true;                               \
>                         break;                                          \
>                 }                                                       \
>                 cpu_relax();                                            \
>         } while (time_before(end_jiffies, jiffies));                    \
>         succeeded;                                                      \
>         })
>
>
>   is it just me, or do those arguments to time_before() look
> backwards?

  with a quick grep, i found one other example that looks reversed.
from drivers/char/hvsi.c:

static void hvsi_drain_input(struct hvsi_struct *hp)
{
        uint8_t buf[HVSI_MAX_READ] __ALIGNED__;
        unsigned long end_jiffies = jiffies + HVSI_TIMEOUT;

        while (time_before(end_jiffies, jiffies))
                if (0 == hvsi_read(hp, buf, HVSI_MAX_READ))
                        break;
}


  surely that's backwards as well, no?

rday
--


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

  reply	other threads:[~2009-12-31 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31 16:40 backwards busy wait using "time_before()"?? Robert P. J. Day
2009-12-31 19:23 ` Robert P. J. Day [this message]
2010-01-01 15:17 ` Andi Kleen

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=alpine.LFD.2.00.0912311421290.5803@localhost \
    --to=rpjday@crashcourse.ca \
    --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