From: Walt Drummond <drummond@engr.valinux.com>
To: george anzinger <george@mvista.com>
Cc: drummond@engr.valinux.com, Hubertus Franke <frankeh@us.ibm.com>,
mingo@elte.hu, Linux Kernel List <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Bug in sys_sched_yield
Date: Mon, 16 Apr 2001 09:03:16 -0700 [thread overview]
Message-ID: <15067.6084.459899.879345@macallan.engr.valinux.com> (raw)
In-Reply-To: <3AD5E676.CF1C1684@mvista.com>
In-Reply-To: <OFC3243AAE.31877E4B-ON85256A2B.006AE9C3@pok.ibm.com> <3AD5D311.5BFE39A6@mvista.com> <15061.56474.247739.99673@macallan.engr.valinux.com> <3AD5E676.CF1C1684@mvista.com>
george anzinger writes:
> All that is cool. Still, most places we don't really address the
> processor, so the logical cpu number is all we need. Places like
> sched_yield, for example, should be using this, not the actual number,
> which IMO should only be used when, for some reason, we NEED the hard
> address of the cpu. I don't think this ever has to leak out to the
> common kernel code, or am i missing something here.
No your not, I was. I completely misinterpreted your question.
Sorry about that.
Hubertus and Kanoj have provided the answer I should have given.
--Walt
next prev parent reply other threads:[~2001-04-16 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 19:31 Bug in sys_sched_yield Hubertus Franke
2001-04-11 20:12 ` Andrea Arcangeli
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 [this message]
[not found] <OF33FEDED1.EDF6D260-ON85256A2D.006D99DE@pok.ibm.com>
2001-04-15 17:23 ` Kanoj Sarcar
2001-04-16 16:00 ` 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=15067.6084.459899.879345@macallan.engr.valinux.com \
--to=drummond@engr.valinux.com \
--cc=frankeh@us.ibm.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).