• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How long do render callbacks have to execute?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How long do render callbacks have to execute?


  • Subject: Re: How long do render callbacks have to execute?
  • From: Brian Willoughby <email@hidden>
  • Date: Fri, 19 Aug 2011 02:08:48 -0700


On Aug 19, 2011, at 01:43, tahome izwah wrote:
2011/8/19 Brian Willoughby <email@hidden>:
On Aug 18, 2011, at 22:53, tahome izwah wrote:
2011/8/13 Brian Willoughby <email@hidden>:
In general, a processor cannot carry out any operations in parallel.

Not true. That is exactly what SIMD instructions do which are built into all modern CPUs.

SIMD does not carry out multiple operations, it performs the same operation
on multiple data values. Single Instruction Multiple Data. Have you
actually written any code using SIMD? How familiar are you with how it
works?

Very. SIMD instructions carry out the same instruction on multiple data *in parallel*. This is contrary to your statement that "a processor cannot carry out any operations in parallel".

As I see it, what you were saying is at best imprecise, but actually
totally wrong, which is my whole point here.


Your point keeps changing. At first you claimed that AUEffectBase kernels were designed to allow processing to be spread across multiple cores. That is simply not true. Now you're trying to quibble as if carrying out one operation on parallel data is the same thing as carrying out multiple operations on multiple cores. So, a processor can carry out a single operation in parallel, but not "operations." In any case, when a single core executes one SIMD operation on 128 bits of data, it's nothing at all in common with multiple cores executing operations in parallel. The code needed to achieve each of these concepts is vastly different. I really don't understand why you're continuing to argue when this has nothing to do with the OP's question or even your original, flawed assertion.

B

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: How long do render callbacks have to execute?
      • From: tahome izwah <email@hidden>
References: 
 >How long do render callbacks have to execute? (From: Jonathan <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: Brian Willoughby <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: Jonathan <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: Brian Willoughby <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: tahome izwah <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: Brian Willoughby <email@hidden>)
 >Re: How long do render callbacks have to execute? (From: tahome izwah <email@hidden>)

  • Prev by Date: Re: How long do render callbacks have to execute?
  • Next by Date: Re: How long do render callbacks have to execute?
  • Previous by thread: Re: How long do render callbacks have to execute?
  • Next by thread: Re: How long do render callbacks have to execute?
  • Index(es):
    • Date
    • Thread