Heads up, BDB coming, needed to support fast configuration
Chris Hegarty
chris.hegarty at oracle.com
Thu May 10 14:04:26 PDT 2012
Thanks Kelly, I appreciate your time going through this.
On 10/05/12 20:08, Kelly O'Hair wrote:
> As far as the current old Makefiles, this looks pretty good and complete.
> Proof is in the pudding though, (where did that phrase come from?) does it build and work? ;^)
It builds on all platforms (even Mac and linux-arm!), with and without
the bdb repo where the system has the bdb develop package installed.
Partial builds that import from another JDK are still not implemented,
I'm not sure if this still makes sense going forward with the new build
system. Anyway, this requires further work, not a blocker for an initial
push.
Oh, here is a link to the main bdb Makefile, maybe you could skim it for
obvious problems?
http://cr.openjdk.java.net/~chegar/jigsaw/bdb_webrev.00/bdb_repo_webrev/webrev/make/Makefile.html
> And more importantly, we need to integrate BDB building into the build-infra work.
Yes, of course. I haven't spent any time on this yet since jigsaw
current doesn't build with the new build. I know the build-infra folks
are working on this. I hope to sync up with them once this is pushed.
> I'll CC Erik and Magnus to make sure they see this. May need to add the BDB repository to build-infra.
Yes, or we could do it in jigsaw/jigsaw first. It is up to date with the
latest jdk8.
-Chris.
>
> -kto
>
> On May 10, 2012, at 7:26 AM, Chris Hegarty wrote:
>
>> Here is there webrev to support building of the bdb repository.
>> http://cr.openjdk.java.net/~chegar/jigsaw/bdb_webrev.00/webrev/
>>
>> -Chris.
>>
>> On 08/05/2012 17:41, Chris Hegarty wrote:
>>> Hi,
>>>
>>> A while back it was pointed out that the configuration data for modules
>>> with entry points is stored in a highly inefficient manner [1]. It was
>>> pointed out at the time that the plan has always been to replace this
>>> with a "fast configuration", based on a persistent b-tree implementation.
>>>
>>> The b-tree implementation that we plan to use is a small footprint
>>> implementation of Berkeley DB [2], called Restricted Data Store (RDS).
>>> It is a minimal build of Berkeley DB that supports only b-tree access,
>>> and provides a simple Java interface to support the functionality
>>> required by the runtime (Jigsaw will also use the native interface). I'm
>>> currently preparing to push the BDB code to Jigsaw. It will live in its
>>> own repository, jigsaw/jigsaw/bdb. This mail is just a heads-up that
>>> this will be coming soon. Note that as BDB is provided in some
>>> distributions, Linux for example, the changes that are coming can use
>>> the installed BDB as an alternative.
>>>
>>> -Chris.
>>>
>>> [1]
>>> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2012-March/002292.html
>>> [2]
>>> http://www.oracle.com/technetwork/products/berkeleydb/overview/index.html
>>>
>
More information about the jigsaw-dev
mailing list