Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/SpecialProjects"

m (Java Chip Integration)
m (Java Chip Integration)
Line 22: Line 22:
 
* [http://developer.amd.com/zones/OpenCLZone/Pages/default.aspx OpenCL] is a standard API for general purpose programming across multicore CPU's, Vector based GPU's and other heterogeneous parallel processors.  In the event that EclipseLink becomes more ''architecture aware'' and requires the use of possibly '''SIMD''' processing.
 
* [http://developer.amd.com/zones/OpenCLZone/Pages/default.aspx OpenCL] is a standard API for general purpose programming across multicore CPU's, Vector based GPU's and other heterogeneous parallel processors.  In the event that EclipseLink becomes more ''architecture aware'' and requires the use of possibly '''SIMD''' processing.
 
====Java Chip Integration====
 
====Java Chip Integration====
*Develop hardware to directly execute Java bytecode (like the [http://en.wikipedia.org/wiki/ARM9E ARM 9E])
+
*Develop hardware to directly execute Java bytecode (like the [http://en.wikipedia.org/wiki/ARM9E ARM 9E] via [http://en.wikipedia.org/wiki/Jazelle Jazelle])
  
 
==References==
 
==References==

Revision as of 13:04, 27 October 2010

EclipseLink Special Projects Group

  • DISCLAIMER: This page reflects investigation into how EclipseLink technology can used as part of - or benefit from integration with other projects. It does NOT imply any formal certification from EclipseLink on these technologies or make any assumptions on the direction of the API. This page is purely experimental speculation.
  • This page details initiatives or projects that use or could benefit from using EclipseLink technology.
  • The scope of projects here also involves any that are experimental in the areas of performance, scalability, platform and hardware aware algorithms.

Projects

Projects In Development

Distributed RMI

Distributed Automata

Requirements
  • This simple application will serve as a test platform to experiment with a distributed SE or EE application so we can test various communication schemes between the physically distributed processing cores.
  • A very simple data model consisting of a planar grid of SIMD ALU units will be partitioned among a group of Java Virtual Machines (both local and remote).
  • We will not use a 2nd level cache as of yet like Coherence or Terracotta to handle inter-VM synchronization until we understand the problem space
Design
Implementation
Testing

Projects In Analysis

Projects Not Started

OpenCL Integration

  • OpenCL is a standard API for general purpose programming across multicore CPU's, Vector based GPU's and other heterogeneous parallel processors. In the event that EclipseLink becomes more architecture aware and requires the use of possibly SIMD processing.

Java Chip Integration

  • Develop hardware to directly execute Java bytecode (like the ARM 9E via Jazelle)

References

Back to the top