Re: Simplest open source database to make lock-free
From: Joe Seigh <jseigh_01_at_xemaps.com>
Date: Mon, 20 Feb 2006 10:37:52 -0500
Message-ID: <nJ6dnbUDattFfGTenZ2dnUVZ_sydnZ2d_at_comcast.com>
>
>
> You think so? If the system in question is properly modularized and small
> enough, you might away without too much work.
>
That's what I was hoping for. Particularly with respect to the data structures since that's the thing lock-free really works off of. If there's a clean and well modularized api, it's easier than if the code accesses the data structures directly from about 500 different places.
Date: Mon, 20 Feb 2006 10:37:52 -0500
Message-ID: <nJ6dnbUDattFfGTenZ2dnUVZ_sydnZ2d_at_comcast.com>
Knut Stolze wrote:
> Christopher Browne wrote:
>
>
>>Oops! Joe Seigh <jseigh_01_at_xemaps.com> was seen spray-painting on a wall: >> >>>What open source databases would be good candidates >>>to reimplement as lock-free (or mostly so)? >> >>I'd think that that represents a sufficiently extensive change that >>you'd likely have to create something new from scratch.
>
>
> You think so? If the system in question is properly modularized and small
> enough, you might away without too much work.
>
That's what I was hoping for. Particularly with respect to the data structures since that's the thing lock-free really works off of. If there's a clean and well modularized api, it's easier than if the code accesses the data structures directly from about 500 different places.
-- Joe Seigh When you get lemons, you make lemonade. When you get hardware, you make software.Received on Mon Feb 20 2006 - 16:37:52 CET