Re: Importing libck

2014-07-21 Thread Phil Sorber
On Tue, May 20, 2014 at 10:12 PM, Leif Hedstrom wrote: > > On May 19, 2014, at 2:19 PM, Samy Al Bahra wrote: > > > (also CK supports 32-bit architectures) > > > > > > > I believe the concern were around some containers which were 64-bit only? > But alas, I don’t think it was a big issue (but I’m

Re: Importing libck

2014-05-20 Thread Leif Hedstrom
On May 19, 2014, at 2:19 PM, Samy Al Bahra wrote: > (also CK supports 32-bit architectures) > > I believe the concern were around some containers which were 64-bit only? But alas, I don’t think it was a big issue (but I’m not very familiar with libck). — leif

Re: Importing libck

2014-05-19 Thread Samy Al Bahra
(also CK supports 32-bit architectures)

Re: Importing libck

2014-05-16 Thread Samy Al Bahra
Phil Sorber writes: > > I'd like to propose that we pull libck into our tree and use it to replace > some of our stuff like the freelist, ink_atomic_list and hash tables. > > http://concurrencykit.org/ > > Right now there are not enough distro's to make just linking against system > libs feasi

Re: Importing libck

2014-04-12 Thread Brian Geffon
Phil is correct, while discussing ck and the architectures it supports we proposed dropping 32bit support independent of ck. Brian On Saturday, April 12, 2014, Phil Sorber wrote: > On Sat, Apr 12, 2014 at 2:00 PM, James Peach > > wrote: > > > On Apr 11, 2014, at 11:34 AM, Phil Sorber > > wrote:

Re: Importing libck

2014-04-12 Thread Phil Sorber
On Sat, Apr 12, 2014 at 2:00 PM, James Peach wrote: > On Apr 11, 2014, at 11:34 AM, Phil Sorber wrote: > > > I'd like to propose that we pull libck into our tree and use it to > replace > > some of our stuff like the freelist, ink_atomic_list and hash tables. > > > > http://concurrencykit.org/ >

Re: Importing libck

2014-04-12 Thread James Peach
On Apr 11, 2014, at 11:34 AM, Phil Sorber wrote: > I'd like to propose that we pull libck into our tree and use it to replace > some of our stuff like the freelist, ink_atomic_list and hash tables. > > http://concurrencykit.org/ > > Right now there are not enough distro's to make just linking a

Re: Importing libck

2014-04-11 Thread Alan M. Carroll
+1 > I'd like to propose that we pull libck into our tree and use it to replace > some of our stuff like the freelist, ink_atomic_list and hash tables. > http://concurrencykit.org/ > Right now there are not enough distro's to make just linking against system > libs feasible, but I'd like to set

Re: Importing libck

2014-04-11 Thread Brian Geffon
+ 1 On Friday, April 11, 2014, Leif Hedstrom wrote: > +1 > > -- Leif > > On Apr 11, 2014, at 12:34 PM, Phil Sorber > > wrote: > > > I'd like to propose that we pull libck into our tree and use it to > replace > > some of our stuff like the freelist, ink_atomic_list and hash tables. > > > > http:

Re: Importing libck

2014-04-11 Thread Leif Hedstrom
+1 — Leif On Apr 11, 2014, at 12:34 PM, Phil Sorber wrote: > I'd like to propose that we pull libck into our tree and use it to replace > some of our stuff like the freelist, ink_atomic_list and hash tables. > > http://concurrencykit.org/ > > Right now there are not enough distro's to make ju

Re: Importing libck

2014-04-11 Thread Theo Schlossnagle
+1 On Fri, Apr 11, 2014 at 12:34 PM, Phil Sorber wrote: > I'd like to propose that we pull libck into our tree and use it to replace > some of our stuff like the freelist, ink_atomic_list and hash tables. > > http://concurrencykit.org/ > > Right now there are not enough distro's to make just li