Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
07/31/10 15:48
Read: times


 
#177549 - processor/processing, and absolute time contra clock cycles
Responding to: ???'s previous message
Note that you must separate DSP into two things.
- Digital Signal Processor (a DSP)
- Digital Signal Processing (to perform DSP)

Any processor can perform Digital Signal Processing.

A Digital Signal Processor on the other hand is a processor that is designed with special capabilities. Adding a MAC will improve the processing abilities, but is not enough to make something into a DSP.

Compare. There once was the 8087 FPU. A special co-processor for floating point. But on the other hand - the 8086 could compute floating point values too without any FPU. But it had to rely on software emulation instead of hardware for the job.

Same with a GPU. Hardware designed for graphics - but a standard prcessor can also draw graphics directly in RAM without any GPU.

I do disagree with
Per Westermark said:A microprocessor may be just as good at handling interrupts quickly - after all, the time spent handling an interrupt is time not spent running the main program.

The whole essence is that the pipelined architecture means that the uprocessor will be further behind than the ucontroller.

Correct. But 3GHz and 9 ticks of pipeline is 3 ns. 100MHz and 1 tick is 10 ns. And a number of microcontrollers have unbreakable instructions of varying clock length meaning that they don't guarantee that they start the interrupt handler directly on the next clock cycle, but may have a jitter of one or two clock cycles depending on the current instruction when the interrupt arrived. A number of GP processors also have multiple register banks or sliding windows of registers, allowing them to start handling an ISR without saving registers, similar to the 8051.

So in the end, the guaranteed worst-case absolute time for taking care of an interrupt can many times be lower in the high-end GP processors than in a microcontroller.

The big problem with GP processors is that when they are mated with GP operating systems, they are often run with interrupts disabled for very significant amounts of times. It's the OS that is the main reason for the loss of real-time behaviour.

List of 15 messages in thread
TopicAuthorDate
µ-controllers, µ-processors and DSPs            01/01/70 00:00      
   No-on last question.            01/01/70 00:00      
      early DSP's had no converters            01/01/70 00:00      
      Signal Processing            01/01/70 00:00      
         Digitial signal processing is mainly math.            01/01/70 00:00      
   it's all marketing            01/01/70 00:00      
   There really isn't a true distinction anymore.            01/01/70 00:00      
      8051 + MAC            01/01/70 00:00      
         I know.            01/01/70 00:00      
   There is some confusion....            01/01/70 00:00      
      DSP designed for concurrency of simple operations            01/01/70 00:00      
         Still some confusion...            01/01/70 00:00      
            processor/processing, and absolute time contra clock cycles            01/01/70 00:00      
               You're being too practical            01/01/70 00:00      
                  No magic ISR advantage for uC in relation to uP            01/01/70 00:00      

Back to Subject List