From: Jun Sun <jsun@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Song Wang <wsonguci@yahoo.com>,
linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: 2.6 preemptive kernel on mips
Date: Wed, 4 Aug 2004 15:25:06 -0700 [thread overview]
Message-ID: <20040804152506.C6269@mvista.com> (raw)
In-Reply-To: <20040804215140.GP9235@smtp.west.cox.net>; from trini@kernel.crashing.org on Wed, Aug 04, 2004 at 02:51:40PM -0700
On Wed, Aug 04, 2004 at 02:51:40PM -0700, Tom Rini wrote:
> On Tue, Aug 03, 2004 at 12:40:48PM -0700, Jun Sun wrote:
>
> > On Tue, Aug 03, 2004 at 12:22:44PM -0700, Song Wang wrote:
> > > Hi,
> > >
> > > Has anyone tried to enable kernel preemption on
> > > Linux mips 2.6 kernel (mips32) and test it? If
> > > so, which version does it work?
> > >
> > > I tried on 2.6.3 and it didn't work.
> > >
> >
> > Try the latest kernel. I checked preemption around 2.6.5 time
> > and I believe all the obvious problems are fixed then.
> >
> > There are still some issues with both SMP and PREEMPT, but most
> > people won't see them in normal cases.
>
> MIPS or generic? It's claimed, at least, that SMP&&PREEMPT have no
> fatal, generic, issues now (I forget if that was the case around 2.6.5).
>
It is MIPS specific problems I was referring to (such as unsafe
smp_processor_id() reference etc).
If you think about it the real problem is that kernel has non-migratable
regions, a section where process should not migrate from one CPU to
another. Before preemtible kernel is introduced such non-migratable
regions are not a problem because they can't migrate during those
regions.
So a potentially better solution is to introduce non-migratable
regions during which scheduler promises not to migrate the processes.
Under such promises a process can actually be preempted while
it is in such a region.
Jun
next prev parent reply other threads:[~2004-08-04 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 19:22 2.6 preemptive kernel on mips Song Wang
2004-08-03 19:40 ` Jun Sun
2004-08-04 21:51 ` Tom Rini
2004-08-04 22:25 ` Jun Sun [this message]
2004-10-04 12:15 ` Atsushi Nemoto
2004-10-05 0:00 ` Jun Sun
2004-10-05 4:58 ` Atsushi Nemoto
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=20040804152506.C6269@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=trini@kernel.crashing.org \
--cc=wsonguci@yahoo.com \
/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