Ticks per timeslice issue

[Mohammed Khoory]

Interesting.. was not aware that the console worked this way. Thanks for the
information.

I've worked around it by having the shell run at the same priority as the
blocking tasks. It's not as responsive anymore and it's not exactly a
solution, but it works. I'm going to take a look at the BSP code sometime if
the issue crops up again.

>-----Original Message-----
>From: rtems-users-bounces at rtems.org [mailto:rtems-users-
>bounces at rtems.org] On Behalf Of Sebastian Huber
>Sent: Friday, April 12, 2013 6:23 PM
>To: rtems-users at rtems.org
>Subject: Re: Ticks per timeslice issue
>
>Hello Mohammed,
>
>the problem is the polled console driver used by your shell task.  It uses
a busy
>loop to wait for input with a rtems_task_wake_after(1).  This leads to
>constant thread switches.  The Classic API tasks use
>THREAD_CPU_BUDGET_ALGORITHM_RESET_TIMESLICE which resets the time
>budget after each thread switch.
>
>--
>Sebastian Huber, embedded brains GmbH
>
>Address : Dornierstr. 4, D-82178 Puchheim, Germany
>Phone   : +49 89 189 47 41-16
>Fax     : +49 89 189 47 41-09
>E-Mail  : sebastian.huber at embedded-brains.de
>PGP     : Public key available on request.
>
>Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>_______________________________________________
>rtems-users mailing list
>rtems-users at rtems.org
>http://www.rtems.org/mailman/listinfo/rtems-users