mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chase Southwood <chase.southwood@yahoo.com>
Cc: devel@driverdev.osuosl.org, abbotti@mev.co.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Staging: comedi: convert while loop to timeout in ni_mio_common.c
Date: Tue, 14 Jan 2014 15:10:03 -0800	[thread overview]
Message-ID: <20140114231003.GB7877@kroah.com> (raw)
In-Reply-To: <1389735061-24626-1-git-send-email-chase.southwood@yahoo.com>

On Tue, Jan 14, 2014 at 03:31:01PM -0600, Chase Southwood wrote:
> This patch to ni_mio_common.c changes a simple while loop to a timeout,
> which is preferred.
> 
> Signed-off-by: Chase Southwood <chase.southwood@yahoo.com>
> ---
> 
> I removed the extra counter variable this time.  Greg, you mentioned that I could just look at the time that has expired to far, and exit and error out if that exceeds a limit.  Right now I'm just tracking how many times udelay is called, since that seems to conform more to other timeouts in this file, but did you instead want me to use some time function to keep track of actual real time that expires?

Please wrap your lines of text, as that's one very long line :)

The best way to do this is to do:
	unsigned long timeout;
	...
	timeout = jiffies + msec_to_jiffies(500);	/* Or how ever long you want to wait */
	do {
		do something...
		udelay(10);
	} while (time_before(jiffies, timeout);

	or switch the loop around and do:

	while (something hasn't happened) {
		if (time_after(jjiffies, timeout)) {
			we timed out, handle it here;
			break;
		}
		udelay(10);
	}

That's much better than having to count up a "number" and have to look
to see how long you are sleeping for to determine just exactly how long
you are going to have until the loop times out, as your code did.

Make sense?

greg k-h

  reply	other threads:[~2014-01-14 23:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  3:13 [PATCH] Staging: comedi: move trailing statement to next line " Chase Southwood
2014-01-14  3:16 ` Joe Perches
2014-01-14  7:23   ` Dan Carpenter
2014-01-14 11:45     ` Ian Abbott
2014-01-14 11:48 ` Ian Abbott
2014-01-14 19:38 ` [PATCH v2] Staging: comedi: convert while loop to timeout " Chase Southwood
2014-01-14 19:45   ` Joe Perches
2014-01-14 19:50   ` Greg KH
2014-01-14 21:31 ` [PATCH v3] " Chase Southwood
2014-01-14 23:10   ` Greg KH [this message]
2014-01-15  0:23 ` [PATCH v4] " Chase Southwood
2014-01-15  3:58   ` Greg KH
2014-01-15 10:29     ` Ian Abbott
2014-01-15 18:29     ` Hartley Sweeten
2014-01-16  2:30       ` Greg KH
2014-01-16 11:08         ` Ian Abbott
2014-01-15  5:15 ` [PATCH v5] " Chase Southwood
2014-01-15 10:38   ` Ian Abbott
2014-01-15 17:51 ` [PATCH v6] " Chase Southwood
2014-01-15 18:48   ` Hartley Sweeten
2014-01-15 19:22 ` [PATCH v7] " Chase Southwood
2014-01-16 11:30   ` Ian Abbott
2014-01-16 17:46     ` Chase Southwood
2014-01-16 18:27 ` [PATCH v8] " Chase Southwood
2014-01-17 13:12   ` Ian Abbott

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=20140114231003.GB7877@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=chase.southwood@yahoo.com \
    --cc=devel@driverdev.osuosl.org \
    --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

Powered by JetHome