All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	Hugh Dickins <hugh@veritas.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: [PATCH 2/3] corruption check: run the corruption checks from a work queue
Date: Tue, 23 Sep 2008 22:54:52 -0700	[thread overview]
Message-ID: <20080923225452.e93186c0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080923215413.0da97008@infradead.org>

On Tue, 23 Sep 2008 21:54:13 -0700 Arjan van de Ven <arjan@infradead.org> wrote:

> 
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Mon, 22 Sep 2008 13:42:15 -0700
> Subject: [PATCH] corruption check: run the corruption checks from a work queue
> 
> the corruption checks are better off run from a work queue; there's nothing
> time critical about them and this way the amount of interrupt-context work
> is reduced.
> 
> ...
>
> +int start_periodic_check_for_corruption(void)
>  {
>  	if (!memory_corruption_check || corruption_check_period == 0)
> -		return;
> +		return 0;
>  
>  	printk(KERN_INFO "Scanning for low memory corruption every %d seconds\n",
>  	       corruption_check_period);
>  
>  	init_timer(&periodic_check_timer);
>  	periodic_check_timer.function = &periodic_check_for_corruption;
> -	periodic_check_for_corruption(0);
> +	mod_timer(&periodic_check_timer,
> +			round_jiffies(jiffies + corruption_check_period*HZ));
> +	return 0;
>  }

Could use schedule_delayed_work() and zap the timer altogether?



  reply	other threads:[~2008-09-24  5:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  4:53 [PATCH 1/3] corruption check: move the corruption checks into their own file Arjan van de Ven
2008-09-24  4:54 ` [PATCH 2/3] corruption check: run the corruption checks from a work queue Arjan van de Ven
2008-09-24  5:54   ` Andrew Morton [this message]
2008-09-24  4:54 ` [PATCH 3/3] corruption check: fix various checkpatch warnings Arjan van de Ven
2008-09-24  5:53 ` [PATCH 1/3] corruption check: move the corruption checks into their own file Andrew Morton
2008-09-24 17:16   ` Arjan van de Ven
2008-09-24 19:36     ` Randy Dunlap
2008-09-25 10:40     ` Ingo Molnar

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=20080923225452.e93186c0.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=hugh@veritas.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    /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.