All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Abylay Ospan <aospan@netup.ru>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] [dvbv5-scan] wait no more than timeout when scanning
Date: Fri, 22 Jul 2016 16:18:51 -0300	[thread overview]
Message-ID: <20160722161851.034752e7@recife.lan> (raw)
In-Reply-To: <1469210077-12313-1-git-send-email-aospan@netup.ru>

Hi Abylay,

Em Fri, 22 Jul 2016 13:54:37 -0400
Abylay Ospan <aospan@netup.ru> escreveu:

> some frontends (mentioned on lgdt3306a) wait timeout inside code like:
> for (i = 20; i > 0; i--) {
>   msleep(50);
> 
> If there is no-LOCK then dvbv5-scan spent a lot of time (doing 40x calls).
> This patch introduce timeout which 4 sec * multiply. So we do not wait more
> than 4 sec (or so) if no-LOCK.
> 
> Signed-off-by: Abylay Ospan <aospan@netup.ru>
> ---
>  utils/dvb/dvbv5-scan.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/utils/dvb/dvbv5-scan.c b/utils/dvb/dvbv5-scan.c
> index 689bc0b..1fc33d7 100644
> --- a/utils/dvb/dvbv5-scan.c
> +++ b/utils/dvb/dvbv5-scan.c
> @@ -182,12 +182,23 @@ static int print_frontend_stats(struct arguments *args,
>  	return 0;
>  }
>  
> +/* return timestamp in msec */
> +uint64_t get_timestamp()
> +{
> +	struct timeval now;
> +	gettimeofday(&now, 0);
> +	return now.tv_sec * 1000 + now.tv_usec/1000;

This is not good, as gettimeofday() is not monotonic, and may be affected
by clock adjustments.

IMHO, the best would be to adjust the do_timeout() to handle
args->timeout_multiply.

Regards,
Mauro

> +}
> +
>  static int check_frontend(void *__args,
>  			  struct dvb_v5_fe_parms *parms)
>  {
>  	struct arguments *args = __args;
>  	int rc, i;
>  	fe_status_t status;
> +	uint64_t start = get_timestamp();
> +	/* msec timeout by default 4 sec * multiply */ 
> +	uint64_t timeout = args->timeout_multiply * 4 * 1000;
>  
>  	args->n_status_lines = 0;
>  	for (i = 0; i < args->timeout_multiply * 40; i++) {
> @@ -203,6 +214,10 @@ static int check_frontend(void *__args,
>  		print_frontend_stats(args, parms);
>  		if (status & FE_HAS_LOCK)
>  			break;
> +
> +		if ((get_timestamp() - start) > timeout)
> +			break;
> +
>  		usleep(100000);

It would also make sense to remove the usleep here and
use something else that would be checking timeout_flag,
like:

	for (i = 1; i < 100; i++) {
		if (timeout_flag)
			break;
		usleep(1000);
	}


-- 
Thanks,
Mauro

  reply	other threads:[~2016-07-22 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 17:54 [PATCH] [dvbv5-scan] wait no more than timeout when scanning Abylay Ospan
2016-07-22 19:18 ` Mauro Carvalho Chehab [this message]
2016-07-25  4:01   ` Abylay Ospan
2016-07-25 18:47   ` Abylay Ospan
  -- strict thread matches above, loose matches on Subject: below --
2016-07-25  3:35 Abylay Ospan

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=20160722161851.034752e7@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=aospan@netup.ru \
    --cc=linux-media@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 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.