On Wed, 2005-11-02 at 09:45 -0500, Carlos Antunes wrote:
> On 11/2/05, Ingo Molnar <[email protected]> wrote:
> >
> > * Carlos Antunes <[email protected]> wrote:
> >
> > > > running the code i simply get:
> > > >
> > > > ~$ ./timing
> > > > Failed to create thread # 382
> >
> > i suspect this is due to the stack ulimit being too high. Try something
> > like 'ulimit -s 128', which will make it 128K, instead of the default
> > 8MB.
> >
>
> Ingo,
>
> First of all, thank you for all the great work you've contributed to
> the Linux community.
>
> Now the question: do you have any ideas about what might make
> SCHED_OTHER perform better than SCHED_FIFO when in the presence of a
Hi Carlos,
Sorry I didn't get back to you sooner. I was already getting ready for
bed last night when you sent me your program. So I'm just getting
around to looking into this now.
To answer your question of why SCHED_OTHER may be preforming better than
SCHED_FIFO (although it shouldn't), probably shows something in either
the timing code, or the priority inheritance. Since a SCHED_OTHER
thread will skip the PI and other things to get it to perform
reliable.
Now could you post/send your CONFIG_FILE. I'm currently getting a test
machine ready to run your program.
Thanks,
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
