On Thu, 10 Jan 2008 09:41:49 -0800 Darren Hart <[EMAIL PROTECTED]> wrote:
> On Thursday 10 January 2008 03:12:31 Sebastien Dugue wrote:
> > The timing measurements take into account threads creation and
> > joining which are performed at SCHED_OTHER priority. This introduce
> > latency artifacts in what we intend to measure.
> >
> > To minimize this effect, bump the main thread priority to just above
> > the matrixmult_thread threads priority (i.e. PRIO + 1).
> >
> > These effects are particularly visible from the concurrent runs as
> > well as the Sequential/Concurrent ratios which exhibit large
> > discrepancies between min, max and average values.
>
> Excellent idea, but reimplemented the set_priority() call from librttest
> with inline posix code. See below:
>
> > +
> > + param.sched_priority = PRIO + 1;
> > + if (sched_setscheduler(0, SCHED_FIFO, ¶m) != 0) {
> > + perror("sched_setscheduler");
> > + return -1;
> > + }
>
> This should be replaced with a call to set_priority(PRIO + 1);
Oops, right, will fix.
>
> Concept Acked, Implementation Nacked.
Thanks,
Sébastien.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
