RE: [2.4.17/18pre] VM and swap - it's really unusable

[Robert Lowery]

Google is your fried ;)

I believe Dawson Engler [e-mail] is the man to contact.  More
info about their project can be found at http://hands.stanford.edu/linux/

You would probably need to give him an example of the bad code you are
trying to catch

-Robert

> -----Original Message-----
> From: george anzinger [mailto:[e-mail]]
> Sent: Tuesday, January 15, 2002 6:52 AM
> To: Robert Lowery
> Cc: [e-mail]; [e-mail]
> Subject: Re: [2.4.17/18pre] VM and swap - it's really unusable
> 
> 
> Robert Lowery wrote:
> > 
> > >I question this because it is too risky to apply. There is 
> no way any
> > >distribution or production system could ever consider applying the
> > >preempt kernel and ship it in its next kernel update 2.4. 
> You never know
> > >if a driver will deadlock because it is doing a test and 
> set bit busy
> > >loop by hand instead of using spin_lock and you cannot 
> audit all the
> > >device drivers out there.
> > 
> > Quick question from a kernel newbie.
> > 
> > Could this audit be partially automated by the Stanford 
> Checker? or would
> > there
> > be too many false positives from other similar looping code?
> > 
> > -Robert
> Sounds like a REALLY good thing (tm) to me.  How do we get them
> interested?
> -- 
> George           [e-mail]
> High-res-timers: http://sourceforge.net/projects/high-res-timers/
> Real time sched: http://sourceforge.net/projects/rtsched/
>