[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ha-dev
Subject:    Re: [Linux-ha-dev] about linux-ha code standard - may I use threads?
From:       Horms <horms () verge ! net ! au>
Date:       2003-07-30 2:58:30
[Download RAW message or body]

On Tue, Jul 29, 2003 at 08:29:01PM -0600, Alan Robertson wrote:
> Horms wrote:
> >On Tue, Jul 29, 2003 at 08:35:50AM -0600, Alan Robertson wrote:
> >
> >>Horms wrote:
> >>
> >>>On Mon, Jul 28, 2003 at 10:25:20PM -0600, Alan Robertson wrote:
> >>>
> >>>>I have good ideas about how to meet that challenge, should it ever come 
> >>>>up. However, most telecom designs seem to concentrate on smaller (4 
> >>>>processors and less) systems and cluster them for scaling.
> >>>
> >>>
> >>>I don't see how this relates to threading at all. Multiple
> >>>processes can be used to parallise thinge in SMP if needed
> >>>(though we don't suport that either).
> >>
> >>Right.  But if you had used a good implementation of threading, this 
> >>would happen for you automatically without having to restructure your 
> >>software. So, in our case, we'll have to adapt some, and in the other 
> >>case we wouldn't.
> >
> >
> >I can't say that I agree with that. Writing treaded programmes requires
> >them to be built with threads in mind from the ground up.  In fact from
> >the underlying libraries up.  You need to implicitly start the threads.
> >And you need to constantly worry about locking (potentially) shared
> >data. I don't see that you get anything for free, except perhaps
> >a headache :-)
> 
> I didn't intend to imply it was free.  It's more like it's included with 
> the (many) headaches ;-)

Sorry, I missunderstood. That I agree with.

> It still CLEARLY doesn't outweigh the other issues.

:-)

-- 
Horms
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.community.tummy.com
http://lists.community.tummy.com/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
[prev in list] [next in list] [prev in thread] [next in thread]