mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] I3 sched tweaks...
Date: Wed, 16 Jan 2002 21:34:39 +1100	[thread overview]
Message-ID: <E16QnOx-0003vt-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Wed, 16 Jan 2002 04:15:47 CDT." <Pine.LNX.4.33.0201160412180.24929-100000@devserv.devel.redhat.com>

In message <Pine.LNX.4.33.0201160412180.24929-100000@devserv.devel.redhat.com> 
you write:
> > 4) scheduler_tick needs no args (p is always equal to current).
> 
> i have not taken this part. We have 'current' calculated in
> update_process_times(), so why not pass it along to the scheduler_tick()
> function?

Because it's redundant.  It's *always* p == current (and the code
assumes this!), but I had to grep the callers to find out.

Moreover, the function doesn't make *sense* if p != current...

> > 3) lock_task_rq returns the rq, rather than assigning it, for clarity.
>
> i've made it an inline function instead of a macro.

I thought of that, but assumed you had a good reason for making it a
macro in the first place...

Thanks!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2002-01-16 10:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16  5:49 Rusty Russell
2002-01-16  9:15 ` Ingo Molnar
2002-01-16  9:17   ` Ingo Molnar
2002-01-16 10:34   ` Rusty Russell [this message]
2002-01-16 21:31     ` Paul Mackerras
2002-01-16 22:46     ` Ingo Molnar
2002-01-16 21:10       ` Robert Love
2002-01-16 21:27         ` Robert Love
2002-01-16 23:31           ` Ingo Molnar
2002-01-16 21:19       ` Justin Carlson
2002-01-17 13:01         ` bill davidsen
2002-01-17  3:37       ` Rusty Russell

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=E16QnOx-0003vt-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®