public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: george anzinger <george@mvista.com>
Cc: Rik van Riel <riel@conectiva.com.br>, SodaPop <soda@xirr.com>,
	alexey@datafoundation.com, linux-kernel@vger.kernel.org
Subject: Re: [test-PATCH] Re: [QUESTION] 2.4.x nice level
Date: Thu, 12 Apr 2001 23:51:45 +0000	[thread overview]
Message-ID: <20010412235144.A43@(none)> (raw)
In-Reply-To: <Pine.LNX.4.21.0104110726210.25737-100000@imladris.rielhome.conectiva> <3AD485E4.40BCBC0D@mvista.com>
In-Reply-To: <3AD485E4.40BCBC0D@mvista.com>; from george@mvista.com on Wed, Apr 11, 2001 at 09:27:16AM -0700

Hi!

> One rule of optimization is to move any code you can outside the loop. 
> Why isn't the nice_to_ticks calculation done when nice is changed
> instead of EVERY recalc.?  I guess another way to ask this is, who needs

This way change is localized very nicely, and it is "obviously right".

-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2001-04-16 12:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 16:12 [QUESTION] 2.4.x nice level SodaPop
2001-04-10  3:37 ` george anzinger
2001-04-10 16:10   ` Rik van Riel
2001-04-10 16:39     ` george anzinger
2001-04-11 10:34     ` [test-PATCH] " Rik van Riel
2001-04-11 15:53       ` Rik van Riel
2001-04-12 22:51         ` Pozsar Balazs
2001-04-11 16:27       ` george anzinger
2001-04-12 23:51         ` Pavel Machek [this message]
2001-04-16 14:18           ` Rik van Riel
2001-04-16 17:49             ` george anzinger

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='20010412235144.A43@(none)' \
    --to=pavel@suse.cz \
    --cc=alexey@datafoundation.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=soda@xirr.com \
    /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