We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
hi; i read the rtx51 specs on the site.it gives context switch for fast task as 70-100 cycles.does this difference come due to priority polling?secondly does context switch is equivalent to 'dispatch latency' form qnx manual?i am asking this because dispatch latency is composed of some other factors plus context switch time. your reply is eagerly awaited pranav phatak
The time difference comes from the fact that there are different configuration options with different number of interrupt enable registers. Context switch time refers to the total time that is required to stop the current task and start the new task.
thank you for your reply.
hi; this is a corollary to the question asked by ppravi.the specs also include note about context switch being dependent on stack load.can you please clarify whether 70-100 microseconds spec refers to switch between fast tasks or between slow task and fast task?i think slow task shall have more load and this switch may take longer.kindly reply as urgently as possible
The task switching time that you have mentioned is the fast task switching time. This does not depend on stack load since fast tasks have their own stack area. If you have furhter questions, please send email to: support.intl@keil.com. Please give us also your address. In this way we can direct you to our local representative and you can discuss things better.
thank you for your co operation nilesh