On Thu, 2006-07-06 at 17:09 +0200, Jan Kiszka wrote:
> > We could do that from the current loop below, given that the
> > accumulation routine is changed to use thread->sched implicitely.
> 
> The idea is avoid adding even further load to the nklock-protected loop.
> And we only update the current thread, not each and every.
> 

Yes, but why? I mean, accumulated time so far remains significant even
for non-running threads.

> > 
> >>    /* Take a snapshot and release the nucleus lock immediately after,
> >>       so that dumping /proc/xenomai/stat with lots of entries won't
> >>       cause massive jittery. */
> >> @@ -359,6 +374,7 @@ static int stat_seq_open(struct inode *i
> >>            iter->stat_info[n].ssw = thread->stat.ssw;
> >>            iter->stat_info[n].csw = thread->stat.csw;
> >>            iter->stat_info[n].pf = thread->stat.pf;
> >> +          iter->stat_info[n].exec_time = thread->stat.exec_time;
> >>    }
> >>  
> >>    xnlock_put_irqrestore(&nklock, s);
> >>
> >>
> >>
> >> _______________________________________________
> >> Xenomai-core mailing list
> >> Xenomai-core@gna.org
> >> https://mail.gna.org/listinfo/xenomai-core
> 
> 
-- 
Philippe.



_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core

Reply via email to