public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>, linux-pm@lists.osdl.org
Subject: Re: [RFC/PATCH 2/2] kernel: don't update load average during snapshot/shutdown
Date: Sat, 28 Apr 2007 00:25:43 +0200	[thread overview]
Message-ID: <20070427222543.GF2994@elf.ucw.cz> (raw)
In-Reply-To: <1177712296.4737.182.camel@nigel.suspend2.net>

Hi!

> > > > NAK. This slows down regular operation, at it is 30 lines for what
> > > > should have been one (or five).
> > > 
> > > Count them. It is one line (an if statement) plus seven lines of
> > > comment.
> > 
> > You count them. Hint... you'll need to read original patch.
> 
> Ah. You're assuming this is the only use of freezer_is_on().

Yes. You need quite good reason for hack like freezer_is_on(), and
this is not it.

> > > > Just place avenrun[0] = avenrun[1] = avenrun[2] = 0 at strategic place
> > > > if you feel strongly about this. Additional points for using Rafael's
> > > > "suspend done" notifier so that you don't have to modify suspend core.
> > > 
> > > =0 might not be right. If you did have a high load average prior to
> > > suspending, not delivering email would be the right thing to do.
> > 
> > Ok, so =0 is not right, but it is better than adding 30lines of junk
> > to the kernel.
> > 
> > NAK on this patch. Original behaviour is acceptable.
> 
> to someone who IIRC correctly recently said he doesn't even use the
> code.

If you want to work with me, learn how to write kernel code, learn
english, and learn how to behave.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-04-27 22:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 13:29 [RFC/PATCH 2/2] kernel: don't update load average during snapshot/shutdown Pekka J Enberg
2007-04-27 14:52 ` Pavel Machek
2007-04-27 14:55   ` Pekka Enberg
2007-04-27 21:32   ` Nigel Cunningham
2007-04-27 22:12     ` Pavel Machek
2007-04-27 22:18       ` Nigel Cunningham
2007-04-27 22:25         ` Pavel Machek [this message]
2007-04-27 23:05           ` Nigel Cunningham
2007-04-28  8:01             ` Pavel Machek
2007-04-28  8:26             ` Pekka Enberg
2007-04-28 10:49               ` Rafael J. Wysocki
2007-04-28 18:07                 ` Rafael J. Wysocki
2007-04-28 22:52                 ` Nigel Cunningham
2007-04-27 15:00 ` Rafael J. Wysocki
2007-04-27 14:59   ` Pekka Enberg
2007-04-27 15:31     ` Rafael J. Wysocki
2007-04-27 15:02   ` Johannes Berg
2007-04-27 15:05     ` Pavel Machek
2007-04-27 15:12       ` Johannes Berg
2007-04-27 15:14         ` Pavel Machek
2007-04-27 15:53         ` Rafael J. Wysocki
2007-04-27 19:56           ` Johannes Berg
2007-04-27 15:16   ` Gautham R Shenoy
2007-04-27 15:30     ` Rafael J. Wysocki

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=20070427222543.GF2994@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=penberg@cs.helsinki.fi \
    /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