From alexanderschunk at t-online.de Mon Sep 3 18:34:00 2007 From: alexanderschunk at t-online.de (alexanderschunk at t-online.de) Date: 03 Sep 2007 18:34 GMT Subject: OpenJDK: JVM and Multicore CPUs Message-ID: <1ISGko-0C4mAq0@fwd33.t-online.de> Hi, i am currently working on a C project that detects various processor features i.g. Hardware multithreading, number of cores, multi-core processor type etc. Currently this C programm only works for Intel processors but i think it could be easily be adopted to AMD processor types. I dont know if Java VM currently supports multithreading or multicore detection at low-level so correct me if i am wrong. - Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From David.Herron at Sun.COM Tue Sep 4 03:37:48 2007 From: David.Herron at Sun.COM (David Herron) Date: Mon, 03 Sep 2007 20:37:48 -0700 Subject: OpenJDK: JVM and Multicore CPUs In-Reply-To: <1ISGko-0C4mAq0@fwd33.t-online.de> References: <1ISGko-0C4mAq0@fwd33.t-online.de> Message-ID: <46DCD30C.40300@sun.com> I suggest bringing this question to the hotspot mailing list. And, yes, it does handle multithreading (e.g. java.lang.Thread) and spreading work over multiple processors or cores. That's one of the reasons the Niagara based systems (T2000 etc) get such great performance, as I understand it, but don't trust me I'm not a hardware guy. - David Herron alexanderschunk at t-online.de wrote: > Hi, > > i am currently working on a C project that detects various processor > features i.g. Hardware multithreading, number of cores, multi-core > processor type etc. > > Currently this C programm only works for Intel processors but i think > it could be easily > be adopted to AMD processor types. > > I dont know if Java VM currently supports multithreading or multicore > detection at low-level > so correct me if i am wrong. > > - Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stephen.Bohne at Sun.COM Tue Sep 4 14:11:48 2007 From: Stephen.Bohne at Sun.COM (Stephen.Bohne at Sun.COM) Date: Tue, 04 Sep 2007 10:11:48 -0400 Subject: OpenJDK: JVM and Multicore CPUs In-Reply-To: <1ISGko-0C4mAq0@fwd33.t-online.de> References: <1ISGko-0C4mAq0@fwd33.t-online.de> Message-ID: <46DD67A4.2090300@Sun.COM> Alex, HotSpot does support it, using mixed assembly/C: http://12.101.252.19/hotspot/xref/src/cpu/i486/vm/vm_version_i486.cpp http://12.101.252.19/hotspot/xref/src/cpu/amd64/vm/vm_version_amd64.cpp Steve alexanderschunk at t-online.de wrote On 09/03/07 14:34,: > Hi, > > i am currently working on a C project that detects various processor > features i.g. Hardware multithreading, number of cores, multi-core > processor type etc. > > Currently this C programm only works for Intel processors but i think it > could be easily > be adopted to AMD processor types. > > I dont know if Java VM currently supports multithreading or multicore > detection at low-level > so correct me if i am wrong. > > - Alex From Paul.Hohensee at Sun.COM Tue Sep 4 14:14:17 2007 From: Paul.Hohensee at Sun.COM (Paul Hohensee - Java SE) Date: Tue, 04 Sep 2007 10:14:17 -0400 Subject: OpenJDK: JVM and Multicore CPUs In-Reply-To: <46DD67A4.2090300@Sun.COM> References: <1ISGko-0C4mAq0@fwd33.t-online.de> <46DD67A4.2090300@Sun.COM> Message-ID: <46DD6839.3080609@sun.com> And in addition (I duplicated Steve's list) src/share/vm/runtime/vm_version.* src/cpu//vm/vm_version_.* where == sparc, i486, amd64 src/share/vm/runtime/os.* Look at numa*(), processor_count(), is_MP() src/os//vm/os_.* where == solaris, linux, win32 Paul Stephen.Bohne at Sun.COM wrote: > Alex, > > HotSpot does support it, using mixed assembly/C: > > http://12.101.252.19/hotspot/xref/src/cpu/i486/vm/vm_version_i486.cpp > http://12.101.252.19/hotspot/xref/src/cpu/amd64/vm/vm_version_amd64.cpp > > Steve > > alexanderschunk at t-online.de wrote On 09/03/07 14:34,: > >> Hi, >> >> i am currently working on a C project that detects various processor >> features i.g. Hardware multithreading, number of cores, multi-core >> processor type etc. >> >> Currently this C programm only works for Intel processors but i think it >> could be easily >> be adopted to AMD processor types. >> >> I dont know if Java VM currently supports multithreading or multicore >> detection at low-level >> so correct me if i am wrong. >> >> - Alex >> > > From langel at redhat.com Tue Sep 4 18:44:46 2007 From: langel at redhat.com (Lillian Angel) Date: Tue, 04 Sep 2007 14:44:46 -0400 Subject: Java Crypto Encumberance Update. In-Reply-To: <46A7F858.7090401@sun.com> References: <46A7F858.7090401@sun.com> Message-ID: <46DDA79E.9070808@redhat.com> Hi, > Here's a quick update on our efforts to remove the cryptographic > encumbrances from the Java SE code base, and thus finally open source > the crypto framework and the Sun providers (SunJCE, PKCS11, MSCAPI). > > We have cleared our concerns with the various stakeholders (legal, > export, mgmt, etc), and began merging the JCE and Java SE code bases > last week. This includes opening the PKCS11/MSCAPI bulk cryptographic > routines also. > > Assuming we don't get pulled in too many different directions or hit any > major snags, we should have this code ready by mid-Sept. Will the code be ready for the next release? > > I know this code has been eagerly anticipated, so thanks for your > patience. We had quite a few items to resolve. > Thank you very much! Lillian From Bradford.Wetmore at Sun.COM Tue Sep 4 19:19:23 2007 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Tue, 04 Sep 2007 12:19:23 -0700 Subject: Java Crypto Encumberance Update. In-Reply-To: <46DDA79E.9070808@redhat.com> References: <46A7F858.7090401@sun.com> <46DDA79E.9070808@redhat.com> Message-ID: <46DDAFBB.40900@sun.com> Hi Lillian, I'm shooting for getting JCE into B21, which will be promoted roughly Sept 27th. I'll probably have to integrate right after b20 closes, and the bi-weekly promotion schedule makes it a bit later than I was hoping for. Hope this helps. Brad Lillian Angel wrote: > Hi, > > >> Here's a quick update on our efforts to remove the cryptographic >> encumbrances from the Java SE code base, and thus finally open source >> the crypto framework and the Sun providers (SunJCE, PKCS11, MSCAPI). >> >> We have cleared our concerns with the various stakeholders (legal, >> export, mgmt, etc), and began merging the JCE and Java SE code bases >> last week. This includes opening the PKCS11/MSCAPI bulk cryptographic >> routines also. >> >> Assuming we don't get pulled in too many different directions or hit any >> major snags, we should have this code ready by mid-Sept. > > Will the code be ready for the next release? > >> >> I know this code has been eagerly anticipated, so thanks for your >> patience. We had quite a few items to resolve. >> > > > Thank you very much! > Lillian From langel at redhat.com Tue Sep 4 19:24:08 2007 From: langel at redhat.com (Lillian Angel) Date: Tue, 04 Sep 2007 15:24:08 -0400 Subject: Java Crypto Encumberance Update. In-Reply-To: <46DDAFBB.40900@sun.com> References: <46A7F858.7090401@sun.com> <46DDA79E.9070808@redhat.com> <46DDAFBB.40900@sun.com> Message-ID: <46DDB0D8.80703@redhat.com> Hi, Great news! Thanks, Lillian Brad Wetmore wrote: > Hi Lillian, > > I'm shooting for getting JCE into B21, which will be promoted roughly > Sept 27th. I'll probably have to integrate right after b20 closes, and > the bi-weekly promotion schedule makes it a bit later than I was hoping > for. > > Hope this helps. > > Brad > > > Lillian Angel wrote: >> Hi, >> >> >>> Here's a quick update on our efforts to remove the cryptographic >>> encumbrances from the Java SE code base, and thus finally open source >>> the crypto framework and the Sun providers (SunJCE, PKCS11, MSCAPI). >>> >>> We have cleared our concerns with the various stakeholders (legal, >>> export, mgmt, etc), and began merging the JCE and Java SE code bases >>> last week. This includes opening the PKCS11/MSCAPI bulk cryptographic >>> routines also. >>> >>> Assuming we don't get pulled in too many different directions or hit any >>> major snags, we should have this code ready by mid-Sept. >> >> Will the code be ready for the next release? >> >>> >>> I know this code has been eagerly anticipated, so thanks for your >>> patience. We had quite a few items to resolve. >>> >> >> >> Thank you very much! >> Lillian From Bradford.Wetmore at Sun.COM Thu Sep 27 22:26:49 2007 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Thu, 27 Sep 2007 15:26:49 -0700 Subject: Crypto has been added to OpenJDK Message-ID: <46FC2E29.9080707@sun.com> News from the encumbrance-removal front: For those who have already downloaded B21 from openjdk.java.net, you might have already noticed some new code. We have just added the cryptographic code (aka JCE) to the OpenJDK source tree. This includes the framework (javax.crypto and friends), the SunJCE provider, and the crypto portions of the SunPKCS11 and SunMSCAPI providers. The OpenJDK framework does not restrict which cryptographic providers can be used. That will not be appropriate for all situations, so let me stress: Compliance with United States export controls and with local law governing the import/export of products incorporating the JCE in the OpenJDK is the responsibility of the licensee. We (Sun) can not give legal guidance on this issue, so please consult a qualified attorney who specializes in import/export issues. Thanks for your patience during the removal of this encumbrance. Thanks, Brad From Janet.Koenig at Sun.COM Thu Sep 27 23:28:35 2007 From: Janet.Koenig at Sun.COM (Janet Koenig) Date: Thu, 27 Sep 2007 16:28:35 -0700 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FC2E29.9080707@sun.com> References: <46FC2E29.9080707@sun.com> Message-ID: <46FC3CA3.20607@sun.com> That's great news! I know this has been a big challenge so thanks for continuing to drive this and making it happen! Regards, Janet Brad Wetmore wrote: > > News from the encumbrance-removal front: > > For those who have already downloaded B21 from openjdk.java.net, you > might have already noticed some new code. We have just added the > cryptographic code (aka JCE) to the OpenJDK source tree. This > includes the framework (javax.crypto and friends), the SunJCE > provider, and the crypto portions of the SunPKCS11 and SunMSCAPI > providers. > > The OpenJDK framework does not restrict which cryptographic providers > can be used. That will not be appropriate for all situations, so let > me stress: > > Compliance with United States export controls and with local law > governing the import/export of products incorporating the JCE in the > OpenJDK is the responsibility of the licensee. > > We (Sun) can not give legal guidance on this issue, so please consult > a qualified attorney who specializes in import/export issues. > > Thanks for your patience during the removal of this encumbrance. > > Thanks, > > Brad From robilad at kaffe.org Fri Sep 28 10:38:23 2007 From: robilad at kaffe.org (Dalibor Topic) Date: Fri, 28 Sep 2007 12:38:23 +0200 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FC3CA3.20607@sun.com> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> Message-ID: <46FCD99F.9030802@kaffe.org> Janet Koenig wrote: > That's great news! I know this has been a big challenge so thanks for > continuing to drive this and making it happen! > Regards, > Janet Thanks from over here, too. No blog on planetjdk.org on it yet? ;) cheers, dalibor topic From Richard.Sands at Sun.COM Fri Sep 28 15:30:24 2007 From: Richard.Sands at Sun.COM (Rich Sands) Date: Fri, 28 Sep 2007 11:30:24 -0400 Subject: Interesting JavaLobby thread: Improving OpenJDK: Is the process optimized? Message-ID: <46FD1E10.5040404@sun.com> An HTML attachment was scrubbed... URL: From Bradford.Wetmore at Sun.COM Fri Sep 28 16:21:14 2007 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Fri, 28 Sep 2007 09:21:14 -0700 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FCD99F.9030802@kaffe.org> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> <46FCD99F.9030802@kaffe.org> Message-ID: <46FD29FA.40706@sun.com> Dalibor Topic wrote: > Janet Koenig wrote: >> That's great news! I know this has been a big challenge so thanks for >> continuing to drive this and making it happen! >> Regards, >> Janet > > Thanks from over here, too. You're welcome. It was a...challenge, as Janet said. :) > No blog on planetjdk.org on it yet? ;) I've yet to create a blog. It's been on my to-do list for far too long. I would probably end up blogging about my outside pursuits, which might be boring unless you like marching bands, travel, or pyrotechnics (not the internal politics kind, but the ones in the sky). ;) I should really create one, I've got a couple topics that you might be interested in from the internal perspective. I'm one of several gatekeepers, so I started writing a couple ideas down about how our internal "gatekeeper" process works, and the overall process of getting fixes into OpenJDK while making sure the quality stays up. The quality *HAS* to stay up, as people will be betting their businesses (or have already) on the code all of us will be developing. Coding in this project is an awesome responsibility, and one that is sometime lost by people who just want to "play with something." Anyway, this quality perspective is "common knowledge" to us gatekeepers, so it might be worth sharing details about what really goes on in the trenches. It is probably a good topic for a blog rather than this email, so maybe I'll get off my duff and do it soon. Oh, and how the coming switch to Mercurial will rock our internal world. So many build/test scripts to update. Brad P.S. When I had gatekeeper duty years ago, if someone "broke the build," I would hang a hangman's noose made from an power cord over their office doorway. You didn't want the noose, because everyone knew what it meant without saying anything. I haven't quite figured out how to do a virtual noose, so please, just don't "break the build." ;) From robilad at kaffe.org Fri Sep 28 19:08:18 2007 From: robilad at kaffe.org (Dalibor Topic) Date: Fri, 28 Sep 2007 21:08:18 +0200 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FD29FA.40706@sun.com> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> <46FCD99F.9030802@kaffe.org> <46FD29FA.40706@sun.com> Message-ID: <46FD5122.7030305@kaffe.org> Brad Wetmore wrote: > > Dalibor Topic wrote: >> Janet Koenig wrote: >>> That's great news! I know this has been a big challenge so thanks for >>> continuing to drive this and making it happen! >>> Regards, >>> Janet >> >> Thanks from over here, too. > > You're welcome. It was a...challenge, as Janet said. :) I bet. Thank you very much for pushing through. >> No blog on planetjdk.org on it yet? ;) > > I've yet to create a blog. It's been on my to-do list for far too long. > I would probably end up blogging about my outside pursuits, which might > be boring unless you like marching bands, travel, or pyrotechnics (not > the internal politics kind, but the ones in the sky). ;) >From our experience on planet.classpath.org, the 'other' side of the people one's working together in a free software project is pretty important in creating the sort of social glue that binds communities, in particular in virtual ones. ;) > I should really create one, I've got a couple topics that you might be > interested in from the internal perspective. I'm one of several > gatekeepers, so I started writing a couple ideas down about how our > internal "gatekeeper" process works, and the overall process of getting > fixes into OpenJDK while making sure the quality stays up. The quality > *HAS* to stay up, as people will be betting their businesses (or have > already) on the code all of us will be developing. Coding in this > project is an awesome responsibility, and one that is sometime lost by > people who just want to "play with something." Great, I think it would be fascinating to hear more about the processes you have in place internally, and how you see them evolve/adapt for OpenJDK. For those of us outside Sun, the more transparent the 'black process boxes' are, the better we can understand what's going on, and where to assist to get things moving in the right direction, if possible/desirable. > Anyway, this quality perspective is "common knowledge" to us > gatekeepers, so it might be worth sharing details about what really goes > on in the trenches. It is probably a good topic for a blog rather than > this email, so maybe I'll get off my duff and do it soon. Yes, please. ;) > Oh, and how the coming switch to Mercurial will rock our internal world. > So many build/test scripts to update. > > Brad > > P.S. When I had gatekeeper duty years ago, if someone "broke the > build," I would hang a hangman's noose made from an power cord over > their office doorway. You didn't want the noose, because everyone knew > what it meant without saying anything. I haven't quite figured out how > to do a virtual noose, so please, just don't "break the build." ;) Speaking of that ... what sort of an automated build system do you use, and do you plan to make the build status for the different configurations available, a la mozilla's tinderbox [1]? cheers, dalibor topic [1] http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox From Bradford.Wetmore at Sun.COM Sat Sep 29 02:34:31 2007 From: Bradford.Wetmore at Sun.COM (Brad Wetmore) Date: Fri, 28 Sep 2007 19:34:31 -0700 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FD5122.7030305@kaffe.org> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> <46FCD99F.9030802@kaffe.org> <46FD29FA.40706@sun.com> <46FD5122.7030305@kaffe.org> Message-ID: <46FDB9B7.3040605@sun.com> > From our experience on planet.classpath.org, the 'other' side of the > people one's working together in a free software project is pretty > important in creating the sort of social glue that binds communities, in > particular in virtual ones. ;) Good point, I was afraid of appearing vain by posting personal stuff on a work blog. >> Anyway, this quality perspective is "common knowledge" to us >> gatekeepers, so it might be worth sharing details about what really goes >> on in the trenches. It is probably a good topic for a blog rather than >> this email, so maybe I'll get off my duff and do it soon. > > Yes, please. ;) Ok, fair enough, I'll be out of the office for a bit, and will try to get something when I return. > Speaking of that ... what sort of an automated build system do you use, Release Engineering, the folks who do the official builds, and our quality folks are much better funded that we integrators. ;) I and probably most integrators use systems and homebrew scripts accumulated over the years. Each night or just before an integration, I take everything submitted to my Security/Networking gate, sync it with the MASTER gates, then drop everything into a build/test environment I developed. It's a distributed build system, which syncs to a common workspace, then forks off a build/test job to each of the major platforms. I tried to mimic our RE environment, so I do full "control" builds, minus hotspot/install. As for testing, we integrators generally run the tests for our respective functional area(s), including the regression, JCK, and Quality trees. As our build machines are also our development machines, and since JDK is so huge, we just can't test everything. We just don't have the iron for it. There's been some standardization on integration build/test scripts in the past (mainly client), but each gatekeeper generally has completely different requirements so there's a number of integration build/test systems out there. For me, I had to keep some source on a completely different machine and thus do separate subbuilds. I looked at a number of different gatekeeper environments before I decided I'd have to write my own. The other systems just didn't do what I needed without a lot of hacking. > and do you plan to make the build status for the different > configurations available, a la mozilla's tinderbox [1]? Tinderbox looks like a nice setup. I don't know what RE has available. I know they do nightly builds, but don't know what testing is done. That would be something for RE or the quality folks to comment on. JPRT, an internal build system for developers, holds some promise of a common automated build system, but there are still limitations on how much it can do. http://blogs.sun.com/kto/entry/jprt_sun_hardware_is_so Oh, did I mention that gatekeeping is only supposed to be part of our job. We're "full time" developers as well. When people introduce breakage, that directly cuts into the time we have to get "real" work done, like say...*gasp*...opening the JCE source. :) With the amount of code reorganization for OpenJDK and the upcoming transition to mercurial, it's been a...(wait for it...wait for it)...challenge... ;) Gads, that's probably another blog entry I just wrote. I should go get started on that and stop boring you good folks at discuss at openjdk. Brad From David.Herron at Sun.COM Sat Sep 29 04:12:33 2007 From: David.Herron at Sun.COM (David Herron) Date: Fri, 28 Sep 2007 21:12:33 -0700 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FDB9B7.3040605@sun.com> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> <46FCD99F.9030802@kaffe.org> <46FD29FA.40706@sun.com> <46FD5122.7030305@kaffe.org> <46FDB9B7.3040605@sun.com> Message-ID: <46FDD0B1.9010502@sun.com> Brad Wetmore wrote: > >> and do you plan to make the build status for the different >> configurations available, a la mozilla's tinderbox [1]? > > Tinderbox looks like a nice setup. I don't know what RE has > available. I know they do nightly builds, but don't know what testing > is done. That would be something for RE or the quality folks to > comment on. > Some of us have looked into using hudson .. but nothing is firmly settled on what to do with it, whether to host it externally, etc. So far it looks like Hudson is really nifty. Okay, so since Brad gave me my cue ... what does Quality do? Oh, we've already published some pages in the Quality Group section of the openjdk site.. but it only touches the surface. What happens varies based on the component area. The VM SQE team has an extensive set of tests which run every night on (if I remember right) the nightly build of the hotspot workspace. The other teams have various other strategies depending on the needs of their component. One of those is the "PIT" or Pre-Integration Testing. PIT's are performed when a developer thinks they're ready for their code to be checked in. They request a PIT run, and we run some portion of the test suites based on what the change is and which suite is more aligned with the checkin. If it passes the PIT, a 'PIT Certificate' is issued, otherwise the developer is sent back to their code to ponder some more ;-). There's also testing of the promoted build that's currently on a bi-weekly schedule. We do this before you guys see the bits on the public site. - David Herron From neugens at limasoftware.net Sat Sep 29 11:35:54 2007 From: neugens at limasoftware.net (Mario Torre) Date: Sat, 29 Sep 2007 13:35:54 +0200 Subject: Crypto has been added to OpenJDK In-Reply-To: <46FDB9B7.3040605@sun.com> References: <46FC2E29.9080707@sun.com> <46FC3CA3.20607@sun.com> <46FCD99F.9030802@kaffe.org> <46FD29FA.40706@sun.com> <46FD5122.7030305@kaffe.org> <46FDB9B7.3040605@sun.com> Message-ID: <1191065754.3169.12.camel@nirvana.limasoftware.net> Il giorno ven, 28/09/2007 alle 19.34 -0700, Brad Wetmore ha scritto: > Good point, I was afraid of appearing vain by posting personal stuff on > a work blog. As Dalibor said, it's nice to hear real life stories. I'm one of the most boring boys in Classpath, I guess my "tech" entries are 1 out of 6!! And all these photos that goes over mugshot (know mugshot? You should give a look at it)! Luckily I was pretty busy so there were not much entries in the blog in the last few weeks :) > I and probably most integrators use systems and homebrew scripts > accumulated over the years. Each night or just before an integration, I [...] > Oh, did I mention that gatekeeping is only supposed to be part of our > job. We're "full time" developers as well. When people introduce > breakage, that directly cuts into the time we have to get "real" work > done, like say...*gasp*...opening the JCE source. :) With the amount > of code reorganization for OpenJDK and the upcoming transition to > mercurial, it's been a...(wait for it...wait for it)...challenge... ;) Your work sounds really interesting, ...challenging... and rewarding! I would go up to the sky and back to the earth each time a new release is successfully introduced to the world! Surely something that you have to be proud of and that easily propagates down to the chain to all the engineers. > Gads, that's probably another blog entry I just wrote. I should go get > started on that and stop boring you good folks at discuss at openjdk. > > Brad :) Mario -- Lima Software - http://www.limasoftware.net/ GNU Classpath Developer - http://www.classpath.org/ Fedora Ambassador - http://fedoraproject.org/wiki/MarioTorre Jabber: neugens at jabber.org pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Please, support open standards: http://opendocumentfellowship.org/petition/ http://www.nosoftwarepatents.com/