Boost logo

Boost Users :

Subject: Re: [Boost-users] boost::interprocess, shared memory and multi-core
From: QPlace (quiteplace_at_[hidden])
Date: 2008-12-18 18:55:16


Andreas Masur <amasur <at> gmx.de> writes:

>
>
> On Dec 17, 2008, at 10:09 AM, QuitePlace wrote:
>
> > Another look at this question is - should one program the inter-
> > process/inter-
> > thread communication first and worry about multi-core later? Or
> > something
> > should be planned at the development stage?
>
> As with other areas such as exception handling etc., I would advise
> you to take multi-core technology into account at design time.
> Programing efficiently for more than one core is certainly not as easy
> as making cookies and thus if you don't plan up front you are likely
> to lose efficiency later on. Especially in your example about
> interprocess/interthread communications.
>
> Ciao, Andreas
>

This is exactly what worries me. Should that planning be done "outside" of
boost framework? For example, if I am using features provided by ::interconnect
library - how am I suppose to take multi-core technology into account if, say,
"shared memory" already locks me into a solution where I don't have much
control on anything multi-core and where "multi-core" is not even present as a
concept?

Your comments are very much appreciated


Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net