• 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: Self-scheduling threading
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Self-scheduling threading


  • Subject: Re: Self-scheduling threading
  • From: Michael Koehmstedt <email@hidden>
  • Date: Thu, 17 Mar 2005 13:43:09 -0800

Shawn,

If you were in my position, which solution would you look for? I
wouldn't mind using the simplest solution, as long as the performance
is acceptable.

Michael Koehmstedt

On Thu, 17 Mar 2005 07:15:35 -0800, Shawn Erickson <email@hidden> wrote:
>
> On Mar 17, 2005, at 2:06 AM, Michael Koehmstedt wrote:
>
> > I need to be able to break up each thread's timeslice into explicitly
> > schedule mini-threads. Basically exactly like fibers on a win32
> > system.
> [snip]
> > If there is sufficient interest by other community members, I'd like
> > to create an open-source Objective-C framework for this kind of
> > threading model. Whether it means porting an existing C/C++
> > implementation or a new one, I'm up for whatever. I just want a
> > solution that's efficient and features an extremely simple
> > explicitly-scheduled threading model.
>
> Do you really know that their are noticeable gains to be made
> especially given the work it would take?
>
> (can depend greatly on the number of would be blocking calls that you
> are trying to have going in parallel)
>
> On todays processors the length of the switching quantum is extremely
> long compared to the clock rate and IPC. Also the work to do a context
> switch hasn't greatly increased in the number instructions yet the
> clock and IPC have, in other words far less time is really wasted doing
> a context switch.
>
> All I am saying is just be sure it is going to net you much of a gain
> and understand that to program to such a model can be touchy and likely
> make using Cocoa (and other system) frameworks problematic directly
> from any of your "fibres" (don't want them to block the thread you are
> running your fibers in since they have no concept of your fibre).
>
> <http://blogs.msdn.com/larryosterman/archive/2005/01/05/347314.aspx>
>
> -Shawn
>
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Self-scheduling threading
      • From: Bob Ippolito <email@hidden>
References: 
 >Self-scheduling threading (From: Michael Koehmstedt <email@hidden>)
 >Re: Self-scheduling threading (From: Dustin Voss <email@hidden>)
 >Re: Self-scheduling threading (From: Michael Koehmstedt <email@hidden>)
 >Re: Self-scheduling threading (From: Shawn Erickson <email@hidden>)

  • Prev by Date: Re: KVO and isKindOfClass:
  • Next by Date: Creating an admin account
  • Previous by thread: Re: Self-scheduling threading
  • Next by thread: Re: Self-scheduling threading
  • Index(es):
    • Date
    • Thread