From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Config Q?: Preempt Model & Preempt Big Kern Lock
Date: Sun, 18 Nov 2007 14:46:20 -0800 [thread overview]
Message-ID: <4740C0BC.8010303@tlinx.org> (raw)
Not big deal, just some config-validity questions regarding
i386 preemption models and preemption of the big-kern lock.
I.e. the relevant options are:
(PM) "Preemption model", there are 3 choices (i386):
(none) No Forced Preemption (Server)
(vol) Voluntary Preempt (Desktop)
(full) Preemptible Kernel (Low-Latency Desktop)
(PBL) "Preempt The Big Kernel Lock" (hint: use Y for desktop, else N)
===
Are these all "valid" config states? Should they all be valid?
I.e., does it make sense to allow "PM==none && PBL==T" ?
Does it makes sense to allow "(PM==full) && PBL==F" ?
Is the issue of big-kernel-lock preemption of major consequence
these days, or should it work in all cases? Are there cases
where one might want PBL==F? Would they be limited to the
"PM=none" case?
Is this the right place or way to ask such questions, or to
get information?
In asking a similar information question, it seems that it
was preferred that a bug be filed. Is that the case here?
Thanks,
Lin
reply other threads:[~2007-11-18 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4740C0BC.8010303@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox