From: <na...@fa...> - 2004-01-22 02:04:06
|
Hi,all Maybe I haven't expressed my question clearly. I will describe my thought in details. I have seen these system call tests, But these tests mainly test changing, getting or setting a parameter of the scheduler. I think ltp has not enough test for scheduler algorithm and scheduler policy. For example: 1. As we know, Linux have three schedule policies (kernel 2.4.x), such as SCHED_RR, SCHED_FIFO and SCHED_OTHER. I think in the scheduler test we should test them to make sure the scheduler has scheduled the processes in the correct schedule sequence. For example, If we have created several process with schedule policy SCHED_FIFO and with different priority values, I think we should moniter the execution sequence to make sure the scheduler has scheduled these processes correctly. 2. Linux has some schedule points. such as: 1. Process status changed, for example process exit, sleep 2. A new process is created 3. The timeslice of the current process runs out 4. Return from kernel space to user space in system call 5. Return to user space after interrupt process When these conditions met,the scheduer will be called. I think all of these conditions should be tested to make sure whether the scheduler is called to reschedule processes I haven't found these test cases in LTP. I don't know why LTP have no test cases to test these items in schedule module test. Maybe these tests have been implemented by the scheduler designers and implementers. So I just want to know whether these test items is necessary to the scheduler test in LTP. And if you do the scheduler test, how do you want to do that? I need your advices. Your advices are very important to me. Thank a lot. -------- Naoto Yamaguchi > On Tue, 2004-01-20 at 21:09, na...@fa... wrote: > > 1.Why does LTP only have performance test for scheduler? > > Is only performance test for scheduler enough? > Which test are you referring to? > > 2.Are item 2, 3, 4 necessary in the scheduler test? > > Have all of these been tested? When? > > 3.Could you please tell me how the scheduler designer and implementer > test > > the scheduler? > > Or if you do the scheduler test, what will you do? > I don't quite understand what you are asking here, but I get the > impression you may not have seen all of the tests. Have you seen the > syscall tests for: > sched_get_priority_max > sched_getscheduler > sched_setscheduler > sched_get_priority_min > sched_rr_get_interval > sched_yield > sched_getparam > sched_setparam > > There are also other tests that will have an effect on scheduling such > as the nice tests, pthreads tests, process_stress, sched_stress, etc. > > Thanks, > Paul Larson |