mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Nigel Cunningham <nigel@suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: [Suspend2][ 1/2] [Suspend2] Disable load updating during suspending.
Date: Tue, 27 Jun 2006 14:35:33 +0200	[thread overview]
Message-ID: <20060627123533.GA28033@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <200606272216.07960.nigel@suspend2.net>

Hi,

On Tue, Jun 27, 2006 at 10:16:03PM +1000, Nigel Cunningham wrote:
> Hi.
> 
> On Tuesday 27 June 2006 22:07, Pavel Machek wrote:
> > Hi!
> >
> > > Suspend2 uses the cpu very intensively, with the result that the load
> > > average can be quite high when a cycle has just completed. This in turn
> > > can cause problems with mail delivery and other activities that suspend
> > > activities when the load average gets too high. To avoid this, we suspend
> > > updates of the load average while the freezer is on.
> >
> > If we want to do this at all... why not simply set load average to
> > zero when resume is done?
> >
> > After all, system probably was completely idle for quite a while :-).
> 
> Yeah, that's a possibility. Neither seems inherently better to me. Maybe 
> others will come up with an argument for one or the other?

I don't know, why would *any* of the processes running on this system
be concerned with how much time this system has been suspended, thrown in
the fridge, shipped overseas and back and then finally resumed?
The current load average, OTOH, seems to be much more important than the time
spent sitting idle gathering dust, since those processes are still running
(after resume, that is) and caring about what other processes do and
what they thus should or shouldn't do based on the activity of others.

OK, some processes might do a time-based and not load-average-based
evaluation (thus there would be a change in time behaviour after resume),
but OTOH many processes *continue* their running state so the load average
should reflect a *continued* state, not a very drastic change to zero
(and then sharply climbing back up from zeroed state).

BTW, thanks a lot for this incredible patch activity now, Nigel!
(and thanks to all for such a nice functionality!)

Andreas Mohr

  reply	other threads:[~2006-06-27 12:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 16:38 [Suspend2][ 0/2] Freezer Upgrade Nigel Cunningham
2006-06-26 16:38 ` [Suspend2][ 1/2] [Suspend2] Disable load updating during suspending Nigel Cunningham
2006-06-27 12:07   ` Pavel Machek
2006-06-27 12:16     ` Nigel Cunningham
2006-06-27 12:35       ` Andreas Mohr [this message]
2006-06-26 16:38 ` [Suspend2][ 2/2] [Suspend2] Freezer upgrade Nigel Cunningham
2006-06-26 20:01   ` Rafael J. Wysocki
2006-06-26 22:48     ` Nigel Cunningham
2006-06-27 11:09       ` Pavel Machek
2006-06-27 12:13         ` Nigel Cunningham

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=20060627123533.GA28033@rhlx01.fht-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@suspend2.net \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®