• 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: mulithreading, dual-core
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mulithreading, dual-core


  • Subject: Re: mulithreading, dual-core
  • From: Adam Knight <email@hidden>
  • Date: Sun, 25 Feb 2007 12:19:30 -0600

And then your code may wind up being orders of magnitude slower.

The following bit is a good discussion of what the compiler's going to do in various multithreading cases and offers a few ideas to getting past using full locks.

	http://ridiculousfish.com/blog/archives/2007/02/17/barrier/


Adam Knight codepoetry - http://www.codepoetry.net/products/


On Feb 25, 2007, at 10:02 AM, Shawn Erickson wrote:


On Feb 25, 2007, at 7:28 AM, John Daniel wrote:

Learn about the volatile modifier. Your code isn't going to be just multithreaded, it will be parallel. You won't be able to get away with just mutex locks. They will have to be volatile mutex locks.

If you use proper locking you won't need volatile.

-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40pobox.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: mulithreading, dual-core
      • From: John Daniel <email@hidden>
    • Re: mulithreading, dual-core
      • From: Shawn Erickson <email@hidden>
References: 
 >mulithreading, dual-core (From: email@hidden)
 >Re: mulithreading, dual-core (From: John Daniel <email@hidden>)
 >Re: mulithreading, dual-core (From: Shawn Erickson <email@hidden>)

  • Prev by Date: Re: misleading error message triggered by #import line (SOLVED)
  • Next by Date: Re: mulithreading, dual-core
  • Previous by thread: Re: mulithreading, dual-core
  • Next by thread: Re: mulithreading, dual-core
  • Index(es):
    • Date
    • Thread