From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: frankeh@us.ibm.com (Hubertus Franke)
Cc: george@mvista.com (george anzinger),
linux-kernel@vger.kernel.org (Linux Kernel List),
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Bug in sys_sched_yield
Date: Sun, 15 Apr 2001 10:23:31 -0700 (PDT) [thread overview]
Message-ID: <200104151723.KAA30317@google.engr.sgi.com> (raw)
In-Reply-To: <OF33FEDED1.EDF6D260-ON85256A2D.006D99DE@pok.ibm.com> from "Hubertus Franke" at Apr 13, 2001 04:06:16 PM
>
>
> George, while this is needed as pointed out in a previous message,
> due to non-contiguous physical IDs, I think the current usage is
> pretty bad (at least looking from a x86 perspective). Maybe somebody
> can chime in from a different architecture.
>
> I think that all data accesses particularly to __aligned_data
> should be performed through logical ids. There's a lot of remapping
> going on, due to the mix of logical and physical IDs.
>
I _think_ cpu_logical_map() can be deleted from the kernel, and all
places that use it can just use the [0 ... (smp_num_cpus-1)] number.
This is for the generic kernel code. The only place that should need
to convert from this number space to a "physical" space would be the
intercpu interrupt code (arch specific code).
Only a handful of architectures (mips64, sparc*, alpha) do array
lookups for cpu_logical_map() anyway, those probably can be changed
to the x86 definition of cpu_logical_map().
Kanoj
next parent reply other threads:[~2001-04-15 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF33FEDED1.EDF6D260-ON85256A2D.006D99DE@pok.ibm.com>
2001-04-15 17:23 ` Kanoj Sarcar [this message]
2001-04-16 16:00 ` [Lse-tech] Bug in sys_sched_yield Walt Drummond
2001-04-11 19:31 Hubertus Franke
2001-04-12 16:08 ` [Lse-tech] " george anzinger
2001-04-12 16:49 ` Walt Drummond
2001-04-12 17:31 ` george anzinger
2001-04-16 16:03 ` Walt Drummond
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=200104151723.KAA30317@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=frankeh@us.ibm.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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