From: Robert Love <rml@tech9.net>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5: MAX_PRIO cleanup
Date: 23 Apr 2002 14:15:54 -0400 [thread overview]
Message-ID: <1019585756.1470.133.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0204231722330.16139-100000@elte.hu>
On Tue, 2002-04-23 at 11:23, Ingo Molnar wrote:
> On 23 Apr 2002, Robert Love wrote:
>
> > Now the hard part is abstracting sched_find_first_set for an arbitrary
> > MAX_RT_PRIO.
>
> i'd suggest the following: keep the current hand-optimized one for the
> bitrange it's good for, and use the find_bit variant for all other values.
> (We had this before, check out some of the older versions of the O(1)
> scheduler.)
In earlier releases we have
include/asm-i386/mmu_context.h :: sched_find_first_zero_bit
but that seems to operate on a 168-bit bitmap only. Around what time
did we have a routine that operated on arbitrary maps? What name/file?
Thanks,
Robert Love
next prev parent reply other threads:[~2002-04-23 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 2:23 [PATCH] 2.5: MAX_PRIO cleanup Robert Love
2002-04-23 7:53 ` Ingo Molnar
2002-04-23 16:53 ` Robert Love
2002-04-23 15:23 ` Ingo Molnar
2002-04-23 18:15 ` Robert Love [this message]
2002-04-23 16:14 ` Ingo Molnar
2002-04-23 18:24 ` Robert Love
2002-04-23 22:43 ` Robert Love
2002-04-23 20:44 ` Ingo Molnar
2002-04-23 23:03 ` Robert Love
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=1019585756.1470.133.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--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