From: Ingo Molnar <mingo@elte.hu>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] O(1) MQ scheduler J9 patch for IA64
Date: Mon, 04 Feb 2002 19:22:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805985@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805977@msgid-missing>
On Mon, 4 Feb 2002, Erich Focht wrote:
> > Why is there a global change of current->processor to current->cpu?
> > That has knock on effects because #define cpu and references to that
> > macro also have to be changed. I don't see any benefit.
>
> Keith,
> I can only guess that Ingo wanted to see the problematic spots when he
> compiles. I think there was a discussion on linux-kernel ML but I didn't
> follow it, so maybe Ingo can tell us...
the current->processor => current->cpu indeed was such a helper, to find
places that rely on p->cpu. (it's mostly code that has scheduling
relevance.)
renaming ->nice to ->__nice had another purpose, eg. in the -K2 patch
there is no 'nice' field anymore, ->static_prio is used.
Ingo
prev parent reply other threads:[~2002-02-04 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 14:45 [Linux-ia64] O(1) MQ scheduler J9 patch for IA64 Erich Focht
2002-02-02 0:21 ` Keith Owens
2002-02-04 17:21 ` Erich Focht
2002-02-04 19:22 ` Ingo Molnar [this message]
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=marc-linux-ia64-105590698805985@msgid-missing \
--to=mingo@elte.hu \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.