From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: general config preemption Q: preempt-model and Big-Lock Preemption
Date: Fri, 04 Jan 2008 19:25:24 -0800 [thread overview]
Message-ID: <477EF8A4.7010507@tlinx.org> (raw)
A question that comes to mind every time I go through the settings
for "Preemption Model" and "Preempt The Big Kernel Lock".
Do each of the combinations "make sense", or are some "no-ops"?
For model, we have 1) no forced (server), 2) Voluntary (Desktop)
3) preemptible (low-latency Desktop), and for Big Lock Preemption (BLP),
we have "yes" or "no".
Questions:
1) What is the difference between "no forced" and "voluntary"? Doesn't
voluntary normally mean "not forced"?
2) If a process is not preemptible, then it seems this would be "doubly
so" in the kernel when the big-lock is held. So does the big-lock
preemption question have any effect (when preempt-model="no forced").
3) If a process is "fully preemptible" but "BLP=false", is that
much different than "voluntary preemption" & BLP=false? I.e. --
should 'preemptible kernel' also imply "BLP=true"...i.e.
_Should_ (would?) the following change be "somewhat" identical to
current config options:
O1) "Preempt Model"="no-forced preemption" (would set
preempt-big-kern-lock to FALSE and doesn't display that question).
O2) "Voluntary Preemption" (presuming there are voluntary preemption
points in the kernel in places where the big-K-lock is held), then
configuration would still ask whether to "Preempt The Big Kernel Lock".
O3) "Preemptible model"="allow-kernel-preemption" (would set
preempt-big-kern-lock to TRUE and doesn't display that question).
next reply other threads:[~2008-01-05 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 3:25 Linda Walsh [this message]
2008-01-07 6:53 ` general config preemption Q: preempt-model and Big-Lock Preemption Nick Piggin
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=477EF8A4.7010507@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 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.