On Wed, Mar 22, 2000 at 01:04:47PM -0500, William Montgomery wrote:
>
> On Wed, 22 Mar 2000 yodaiken@fsmlabs.com wrote:
>
> > > I say again, the need_resched is _not_ lost. The whole issue is cleanly
> > > resolved by referencing the proper "current" structure when need_resched
> > > is set.
> > >
> > > Please read my previous posts on this thread.
> >
> > My question is why the last part of the scheduler needs to run with interrupts
> > enabled.
> >
> It doesnt need to, it just isnt necessary to disable/spin_lock interrupts
> at that time. Interrupts are only disabled when necessary, this keeps
> interrupt latency low.
But we run perhaps 1000 instructions here during a context switch. The utility
of handling an interrupt during that time is minimal and, as shown, there
are possible bugs that need some interesting fixes.
>
> Wm
-- --------------------------------------------------------- Victor Yodaiken FSMLabs: www.fsmlabs.com www.rtlinux.com FSMLabs is a servicemark and a service of VJY Associates L.L.C, New Mexico.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:36 EST