Re: more on scheduler benchmarks

Joe deBlaquiere wrote: > > Maybe I've been off in the hardware lab for too long, but how about > > 1. using ioperm to give access to the parallel port. > 2. have your program write a byte (thread id % 256 ?) constantly to the > port during it's other activity > 3. capture the results from

Re: more on scheduler benchmarks

Joe deBlaquiere wrote: Maybe I've been off in the hardware lab for too long, but how about 1. using ioperm to give access to the parallel port. 2. have your program write a byte (thread id % 256 ?) constantly to the port during it's other activity 3. capture the results from another

Re: more on scheduler benchmarks

Bill Hartner wrote: > > Hubertus wrote : > > > The only problem I have with sched_yield like benchmarks is that it > creates > > artificial lock contention as we basically spent most of the time other > > then context switching + syscall under the scheduler lock. This we won't > > see in real

Re: more on scheduler benchmarks

Bill Hartner wrote: Hubertus wrote : The only problem I have with sched_yield like benchmarks is that it creates artificial lock contention as we basically spent most of the time other then context switching + syscall under the scheduler lock. This we won't see in real apps, that's

Re: more on scheduler benchmarks

Maybe I've been off in the hardware lab for too long, but how about 1. using ioperm to give access to the parallel port. 2. have your program write a byte (thread id % 256 ?) constantly to the port during it's other activity 3. capture the results from another computer with an ecp port This

Re: more on scheduler benchmarks

On Monday 22 January 2001 10:30, Mike Kravetz wrote: > Last week while discussing scheduler benchmarks, Bill Hartner > made a comment something like the following "the benchmark may > not even be invoking the scheduler as you expect". This comment > did not fully sink in until this weekend when

Re: more on scheduler benchmarks

On Monday 22 January 2001 10:30, Mike Kravetz wrote: Last week while discussing scheduler benchmarks, Bill Hartner made a comment something like the following "the benchmark may not even be invoking the scheduler as you expect". This comment did not fully sink in until this weekend when I

Re: more on scheduler benchmarks

Maybe I've been off in the hardware lab for too long, but how about 1. using ioperm to give access to the parallel port. 2. have your program write a byte (thread id % 256 ?) constantly to the port during it's other activity 3. capture the results from another computer with an ecp port This