public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Jason Uhlenkott <jasonuhl@sgi.com>, Andrew Morton <akpm@osdl.org>,
	holt@sgi.com, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Prezeroing V8 + free_hot_zeroed_page + free_cold_zeroed page
Date: Thu, 17 Mar 2005 21:43:17 -0800	[thread overview]
Message-ID: <29495f1d050317214315f6da3d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503171808540.11258@schroedinger.engr.sgi.com>

On Thu, 17 Mar 2005 18:09:11 -0800 (PST), Christoph Lameter
<clameter@sgi.com> wrote:
> On Thu, 17 Mar 2005, Jason Uhlenkott wrote:
> 
> > On Thu, Mar 17, 2005 at 05:36:50PM -0800, Christoph Lameter wrote:
> > > +        while (avenrun[0] >= ((unsigned long)sysctl_scrub_load << FSHIFT)) {
> > > +           set_current_state(TASK_UNINTERRUPTIBLE);
> > > +           schedule_timeout(30*HZ);
> > > +   }
> >
> > This should probably be TASK_INTERRUPTIBLE.  It'll never actually get
> > interrupted either way since kernel threads block all signals, but
> > sleeping uninterruptibly contributes to the load average.
> 
> Correct. .... I just do not seem to be able to get this right.

I think msleep_interruptible(30000) would be your best choice, then. 
Maybe with a comment that you don't actually expect signals, but are
using TASK_INTERRUPTIBLE to avoid contributing to load average (that
way, if the loadavg calculation changes someday, somebody will be able
to change your sleep over appropriately).

Thanks,
Nish

  reply	other threads:[~2005-03-18  5:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 21:43 [PATCH] Prezeroing V8 Christoph Lameter
2005-03-17 22:08 ` Andrew Morton
2005-03-17 22:31   ` Christoph Lameter
2005-03-17 23:11     ` Andrew Morton
2005-03-17 23:24       ` Christoph Lameter
2005-03-17 23:52         ` Andrew Morton
2005-03-18  0:00           ` Christoph Lameter
2005-03-17 23:26       ` Christoph Lameter
2005-03-17 23:59         ` Andrew Morton
2005-03-18  0:04           ` Christoph Lameter
2005-03-18  0:17             ` Andrew Morton
2005-03-18  0:29               ` Christoph Lameter
2005-03-18  1:36   ` [PATCH] Prezeroing V8 + free_hot_zeroed_page + free_cold_zeroed page Christoph Lameter
2005-03-18  2:06     ` Jason Uhlenkott
2005-03-18  2:09       ` Christoph Lameter
2005-03-18  5:43         ` Nish Aravamudan [this message]
2005-03-17 22:59 ` [PATCH] Prezeroing V8 Nish Aravamudan
2005-03-17 23:06   ` Christoph Lameter
2005-03-18  3:14     ` Benjamin Herrenschmidt
2005-03-25  1:44 ` Pavel Machek
2005-03-25 12:28   ` Jan Engelhardt
2005-03-29  1:50   ` [PATCH] " Christoph Lameter

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=29495f1d050317214315f6da3d@mail.gmail.com \
    --to=nish.aravamudan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=holt@sgi.com \
    --cc=jasonuhl@sgi.com \
    --cc=linux-ia64@vger.kernel.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