On Wed, 22 Jul 2015 10:30:47 +0300, Meyer Lansky said: > I would like to improve the code, but has not found a practical method of finding errors. Bugs in the scheduler almost always manifest in one of two ways: 1) Truly spectacular crashes or hangs where you *know* you've found a bug. 2) Find a workload that it performs poorly (for instance - how does it deal on a 4-core system with 8 processes that use enough memory that together, they push the system into thrashing mode, plus 40 or 50 processes that only want millisecond timeslices - but at a high realtime priority? Can you find other mixes that give it indigestion? You're going to have to learn a lot about process scheduling to find bugs in that code. And when I say a lot, I mean "probably as much as you'd cover in a full-semester college course"....
Attachment:
pgpJS0IVJNLey.pgp
Description: PGP signature
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
