On Wed, 30 Aug 2023 09:23:55 GMT, Leo Korinth wrote:
>> Rename createJavaProcessBuilder so that it is not used by mistake instead of
>> createTestJvm.
>>
>> I have used the following sed script: `find -name "*.java" | xargs -n 1 sed
>> -i -e
>>
On Tue, 24 Oct 2023 11:51:45 GMT, Johan Sjölen wrote:
>> I think that NMT is deserving of its own subdirectory. Can we do a review of
>> the changes before I fix the merge conflicts?
>>
>> 1. Moved all the nmt source code from services/ to nmt/
>> 2. Renamed all the include statements and
On Thu, 26 Oct 2023 09:51:15 GMT, Johan Sjölen wrote:
>> I think that NMT is deserving of its own subdirectory. Can we do a review of
>> the changes before I fix the merge conflicts?
>>
>> 1. Moved all the nmt source code from services/ to nmt/
>> 2. Renamed all the include statements and
On Tue, 5 Sep 2023 18:05:34 GMT, Roger Riggs wrote:
>> I have created an alternative that uses enums to force the user to make a
>> decision:
>> https://github.com/openjdk/jdk/compare/master...lkorinth:jdk:+process_tools
>> . Another alternative is to do the same but instead using an enum (I
On Mon, 18 Sep 2023 20:47:13 GMT, Daniel D. Daugherty
wrote:
> Change the default of LockingMode to LM_LIGHTWEIGHT from LM_LEGACY.
>
> This fix has been tested with 3 Mach5 Tier[1-8] runs and a 4th is in process.
Looks good. Thank you!
-
Marked as reviewed by stefank (Reviewer).
On Thu, 19 Oct 2023 20:06:50 GMT, Johan Sjölen wrote:
> I think that NMT is deserving of its own subdirectory. Can we do a review of
> the changes before I fix the merge conflicts?
>
> 1. Moved all the nmt source code from services/ to nmt/
> 2. Renamed all the include statements and sorted
On Fri, 20 Oct 2023 11:31:11 GMT, Johan Sjölen wrote:
> For the gtest source files I separated the includes in a consistent manner,
> they all look like this pattern now:
That's not what I see in the latest patch. Could you revert that separation and
then we can consider that style change in
On Mon, 23 Oct 2023 08:34:59 GMT, Johan Sjölen wrote:
>> I think that NMT is deserving of its own subdirectory. Can we do a review of
>> the changes before I fix the merge conflicts?
>>
>> 1. Moved all the nmt source code from services/ to nmt/
>> 2. Renamed all the include statements and
On Fri, 20 Oct 2023 12:49:46 GMT, Johan Sjölen wrote:
>> I think that NMT is deserving of its own subdirectory. Can we do a review of
>> the changes before I fix the merge conflicts?
>>
>> 1. Moved all the nmt source code from services/ to nmt/
>> 2. Renamed all the include statements and
On Tue, 24 Oct 2023 07:49:30 GMT, Leo Korinth wrote:
>> Rename createJavaProcessBuilder so that it is not used by mistake instead of
>> createTestJvm.
>>
>> I have used the following sed script: `find -name "*.java" | xargs -n 1 sed
>> -i -e
>>
On Fri, 25 Aug 2023 09:45:09 GMT, Johan Sjölen wrote:
>> This code looks similar to a capturing lambda. Would an alternative be to
>> use that instead and let the calling code be changed to:
>>
>>
>> int i = lgrp_spaces()->find([&](LGRPSpace* space) {
>> return space->lgrp_id() ==
On Fri, 25 Aug 2023 08:31:58 GMT, Johan Sjölen wrote:
>> src/hotspot/share/utilities/growableArray.hpp line 213:
>>
>>> 211:
>>> 212: template
>>> 213: int find(T* token, bool f(T*, E)) const {
>>
>> Pardon my ignorance here, but what is the type relationship between T and E?
>
> It's
On Mon, 27 Jun 2022 14:14:23 GMT, Stefan Karlsson wrote:
>>> The current approach limits the knowledge of non-strong ref types to
>>> `instanceRefKlass` file.
>>
>> The mechanism used to compute the correct reftype is purely derived from the
>> parser,
On Fri, 24 Jun 2022 00:15:10 GMT, Kim Barrett wrote:
>> `_reference_type` always gets the correct value after the constructor is
>> run. The member initializer list just follows the convention of having all
>> fields set. One could move this field inside the constructor body to ensure
>> this
On Tue, 28 Jun 2022 19:43:33 GMT, Albert Mingkun Yang wrote:
>> Simple rename and some comments update.
>>
>> Test: build
>
> Albert Mingkun Yang has updated the pull request incrementally with four
> additional commits since the last revision:
>
> - arg rename
> - default arg
> - revert
>
On Mon, 27 Jun 2022 22:19:35 GMT, Albert Mingkun Yang wrote:
>> Simple rename and some comments update.
>>
>> Test: build
>
> Albert Mingkun Yang has updated the pull request incrementally with one
> additional commit since the last revision:
>
> review
Looks good. +1 on Kim's latest
On Mon, 27 Jun 2022 22:19:35 GMT, Albert Mingkun Yang wrote:
>> Simple rename and some comments update.
>>
>> Test: build
>
> Albert Mingkun Yang has updated the pull request incrementally with one
> additional commit since the last revision:
>
> review
Scratch my last comment. This
During the discussion of
[JDK-8292981](https://bugs.openjdk.org/browse/JDK-8292981) an opinion was
voiced that we should stop using INTPTR_FORMAT when printing pointers.
Some background that could explain why some tend to use INTPTR_FORMAT instead
of PTR_FORMAT:
Both those format specifiers
On Fri, 2 Sep 2022 09:51:06 GMT, Stefan Karlsson wrote:
> During the discussion of
> [JDK-8292981](https://bugs.openjdk.org/browse/JDK-8292981) an opinion was
> voiced that we should stop using INTPTR_FORMAT when printing pointers.
>
> Some background that could explain why s
used the name AnyObj, as short, simple
> name. I'm open to changing the name to something else.
>
> The patch also adds a new class named ArenaObj, which is for objects only
> allocated in provided arenas.
>
> The patch also removes the need to provide ResourceObj/AnyObj::C_HEAP to
&g
Background to this patch:
This prototype/patch has been discussed with a few HotSpot devs, and I've
gotten feedback that I should send it out for broader discussion/review. It
could be a first step to make it easier to talk about our allocation super
classes and strategies. This in turn would
On Thu, 8 Sep 2022 08:42:30 GMT, Stefan Karlsson wrote:
>> During the discussion of
>> [JDK-8292981](https://bugs.openjdk.org/browse/JDK-8292981) an opinion was
>> voiced that we should stop using INTPTR_FORMAT when printing pointers.
>>
>> Some background th
On Fri, 2 Sep 2022 09:51:06 GMT, Stefan Karlsson wrote:
> During the discussion of
> [JDK-8292981](https://bugs.openjdk.org/browse/JDK-8292981) an opinion was
> voiced that we should stop using INTPTR_FORMAT when printing pointers.
>
> Some background that could explain why s
On Wed, 7 Sep 2022 22:06:11 GMT, Kim Barrett wrote:
> Looks good.
Thanks.
> Also noticed some pre-existing unnecessary (void*) casts of the pointer
> argument to p2i. Not your problem, and not really appropriate for this change
> to do anything about them, but I really hate eye-catching
On Thu, 6 Oct 2022 12:44:23 GMT, Johan Sjölen wrote:
>> Here's a suggested solution for the ticket mentioned and a use case for
>> outputStream. I'm not attached to the name.
>>
>> This saves space for all allocated outputStreams, which is nice. It also
>> makes the purpose of ResourceObj
On Tue, 10 Jan 2023 10:51:14 GMT, Albert Mingkun Yang wrote:
> Simple change of using the actual type for a field.
>
> Test: hotspot_gc
Looks good. Some nits:
src/hotspot/share/gc/serial/tenuredGeneration.hpp line 68:
> 66: void assert_correct_size_change_locking();
> 67:
> 68:
On Tue, 10 Jan 2023 22:50:11 GMT, Justin King wrote:
>> Remove abstraction that is a holdover from Solaris. Direct usages of
>> `MmapArrayAllocator` have been switched to normal `malloc`. The
>> justification is that none of the code paths are called from signal
>> handlers, so using `mmap`
On Wed, 11 Jan 2023 14:27:44 GMT, Justin King wrote:
> ArrayAllocator with ArrayAllocatorMallocLimit removed is effectively
> MallocArrayAllocator. Are you suggesting leaving MallocArrayAllocator and
> MmapArrayAllocator thus update references to ArrayAllocator to be
> MallocArrayAllocator?
On Wed, 11 Jan 2023 20:53:38 GMT, Justin King wrote:
>> Remove abstraction that is a holdover from Solaris. Direct usages of
>> `MmapArrayAllocator` have been switched to normal `malloc`. The
>> justification is that none of the code paths are called from signal
>> handlers, so using `mmap`
On Wed, 14 Dec 2022 22:22:48 GMT, David Holmes wrote:
> This is a simple cleanup RFE to get rid of old-style C casts in relation to
> JavaThread.
>
> In many cases involving NULL/nullptr the cast could just be dropped.
> Sometimes a static cast is needed to disambiguate overloads.
>
> A
On Wed, 7 Dec 2022 11:16:03 GMT, Albert Mingkun Yang wrote:
> Small change of merging two classes to reduce inheritance chain length.
>
> Test: hotspot_gc
Marked as reviewed by stefank (Reviewer).
-
PR: https://git.openjdk.org/jdk/pull/11556
r the include headers I've also cleaned up surrounding
> whitespaces and incorrect include guards.
Stefan Karlsson has updated the pull request with a new target base due to a
merge or a rebase. The pull request now contains four commits:
- Merge remote-tracking branch 'upstream/master' into
On Wed, 16 Nov 2022 16:17:48 GMT, Stefan Karlsson wrote:
>> The sorted blocks of includes have deteriorated to the point that I felt
>> compelled to clean up some of the issues.
>>
>> *EDIT*: The below discussion has been deferred out of this PR. Now this on
On Fri, 11 Nov 2022 14:26:20 GMT, Stefan Karlsson wrote:
> The sorted blocks of includes have deteriorated to the point that I felt
> compelled to clean up some of the issues.
>
> *EDIT*: The below discussion has been deferred out of this PR. Now this only
> deals with fixin
; src/hotspot/share,
just like the other platform-independent headers in HotSpot.
>
> While going over the include headers I've also cleaned up surrounding
> whitespaces and incorrect include guards.
Stefan Karlsson has updated the pull request with a new target base due to a
me
> the header files in src/hotspot/share/include gets included by specifying the
> path from src/hotspot/share, just like the other platform-independent headers
> in HotSpot
.
>
> This RFE splits out the 'include/' changes from #11108 / JDK-8296886, so that
> those changes can be
On Wed, 16 Nov 2022 11:05:59 GMT, Stefan Karlsson wrote:
>> One of the more prevalent issues is that files in src/hotspot/share/include
>> are not properly sorted. There has been some discussion that that was done
>> on purpose, but it just adds another exception to
On Mon, 14 Nov 2022 09:25:11 GMT, Stefan Karlsson wrote:
> One of the more prevalent issues is that files in src/hotspot/share/include
> are not properly sorted. There has been some discussion that that was done on
> purpose, but it just adds another exception to the include rules t
On Fri, 11 Nov 2022 21:01:31 GMT, Kim Barrett wrote:
>> Stefan Karlsson has updated the pull request with a new target base due to a
>> merge or a rebase. The pull request now contains three commits:
>>
>> - Cleanups
>> - Merge remote-tr
On Mon, 14 Nov 2022 11:39:10 GMT, Kim Barrett wrote:
>> src/hotspot/os/windows/jvm_windows.cpp line 27:
>>
>>> 25: #include "precompiled.hpp"
>>> 26: #include "include/jvm.h"
>>> 27: #include "os_windows.hpp"
>>
>> os_windows should be at the end, included using `OS_HEADER("os")`.
>
> But
On Wed, 16 Nov 2022 16:17:48 GMT, Stefan Karlsson wrote:
>> The sorted blocks of includes have deteriorated to the point that I felt
>> compelled to clean up some of the issues.
>>
>> One of the more prevalent issues is that files in src/hotspot/share/include
&g
> the header files in src/hotspot/share/include gets included by specifying the
> path from src/hotspot/share, just like the other platform-independent headers
> in HotSpot
.
>
> This RFE splits out the 'include/' changes from #11108 / JDK-8296886, so that
> those changes can be
On Wed, 25 Jan 2023 11:45:47 GMT, Johan Sjölen wrote:
> Do the conversion in the share/memory/ sub-directory and all of its files.
Marked as reviewed by stefank (Reviewer).
src/hotspot/share/memory/guardedMemory.hpp line 196:
> 194:*/
> 195: void* wrap_with_guards(void* base_ptr, size_t
Today we use mtNone to denote that a GrowableArray should *NOT* be backed by a
CHeap allocated array.
I've gotten feedback that it would probably be good to limit the usage of
mtNone, and at some point maybe completely remove it.
This patch takes a small step to remove mtNone from the
On Fri, 11 Nov 2022 14:26:20 GMT, Stefan Karlsson wrote:
> The sorted blocks of includes have deteriorated to the point that I felt
> compelled to clean up some of the issues.
>
> One of the more prevalent issues is that files in src/hotspot/share/include
> are not properly so
On Fri, 11 Nov 2022 14:26:20 GMT, Stefan Karlsson wrote:
> The sorted blocks of includes have deteriorated to the point that I felt
> compelled to clean up some of the issues.
>
> One of the more prevalent issues is that files in src/hotspot/share/include
> are not properly so
One of the more prevalent issues is that files in src/hotspot/share/include are
not properly sorted. There has been some discussion that that was done on
purpose, but it just adds another exception to the include rules that don't
have any practical purposes, IMHO. It also goes against our
On Mon, 14 Nov 2022 10:15:41 GMT, Erik Österlund wrote:
>> The current loom code makes some assumptions about GC that will not work
>> with generational ZGC. We should make this code more GC agnostic, and
>> provide a better interface for talking to the GC.
>>
>> In particular,
>> 1) All GCs
On Mon, 14 Nov 2022 09:25:11 GMT, Stefan Karlsson wrote:
> One of the more prevalent issues is that files in src/hotspot/share/include
> are not properly sorted. There has been some discussion that that was done on
> purpose, but it just adds another exception to the include rules t
> the header files in src/hotspot/share/include gets included by specifying the
> path from src/hotspot/share, just like the other platform-independent headers
> in HotSpot
.
>
> This RFE splits out the 'include/' changes from #11108 / JDK-8296886, so that
> those changes can be
On Tue, 15 Nov 2022 14:25:15 GMT, Erik Joelsson wrote:
> Build change looks good.
Thanks, Erik. Actually, that change should have been reverted with the last
change. I'll revert that.
-
PR: https://git.openjdk.org/jdk/pull/11133
The sorted blocks of includes have deteriorated to the point that I felt
compelled to clean up some of the issues.
One of the more prevalent issues is that files in src/hotspot/share/include are
not properly sorted. There has been some discussion that that was done on
purpose, but it just adds
On Mon, 24 Apr 2023 08:24:53 GMT, Kim Barrett wrote:
> Please review this change to the string deduplication thread to make it a kind
> of JavaThread rather than a ConcurrentGCThread. There are several pieces to
> this change:
>
> (1) New class StringDedupThread (derived from JavaThread),
On Tue, 11 Apr 2023 11:47:46 GMT, Roman Kennke wrote:
>> src/hotspot/share/runtime/lockStack.inline.hpp line 111:
>>
>>> 109: int end = to_index(_top);
>>> 110: for (int i = end - 1; i >= 0; i--) {
>>> 111: if (NativeAccess<>::oop_load(&_base[i]) == o) {
>>
>> The use of NativeAccess
On Thu, 6 Apr 2023 11:59:45 GMT, Roman Kennke wrote:
>> This change adds a fast-locking scheme as an alternative to the current
>> stack-locking implementation. It retains the advantages of stack-locking
>> (namely fast locking in uncontended code-paths), while avoiding the overload
>> of the
On Tue, 11 Apr 2023 13:48:15 GMT, Roman Kennke wrote:
>> It looks to me like the code could read racingly read the element just above
>> `_top`, which could contain a stale oop. If the address of the stale oop
>> matches the address of `o` then `contains` would incorrectly return true.
>>
>>
On Wed, 12 Apr 2023 02:08:08 GMT, David Holmes wrote:
>> That seems fine to me, as long as we don't crash. But my understanding is
>> that Generational ZGC will crash if it sees a stale oop. Isn't it possible
>> that the racing read sees junk that looks to Generational ZGC like a stale
>>
On Tue, 7 Feb 2023 17:25:02 GMT, Justin King wrote:
>> - Rename `MEMFLAGS` to `MemoryType`. `MEMFLAGS` is highly misleading as
>> flags typically can be combined.
>> - Update `MemoryType` to have enumeration names that follow the style guide,
>> no `mt` prefix.
>> - Create aliases for old
On Wed, 3 May 2023 18:52:19 GMT, Chris Plummer wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix PPC build after 8305668
>
> test/hotspot/jtreg/ProblemList-generational-zgc.txt
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle'
On Wed, 3 May 2023 21:32:54 GMT, Martin Doerr wrote:
> I'm getting build warnings on all linux platforms with gcc-11.3.0:
>
> ```
> src/hotspot/share/gc/z/zDriver.cpp:84:13: error: In the GNU C Library,
> "minor" is defined
> by . For historical compatibility, it is
> currently defined by
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle
On Wed, 3 May 2023 18:57:22 GMT, Chris Plummer wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix PPC build after 8305668
>
> test/jdk/com/sun/jdi/ThreadMemoryLeakTest.ja
On Wed, 3 May 2023 20:00:42 GMT, Chris Plummer wrote:
>> Yes, the test was finicky with the heap size. Given that the leak it tries
>> to provoke would be provoked by other GCs as well, we didn't think it was
>> that important to run this particular test with Generational ZGC. If you
>> still
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
>
On Wed, 3 May 2023 18:54:24 GMT, Chris Plummer wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix PPC build after 8305668
>
> test/jdk/ProblemList-generational-zgc.txt line
When running jstat tests like the following:
test/jdk/sun/tools/jstatd/TestJstatdServer.java
with Generational ZGC we get a failure because the O (old generation
percentage) is reported as `-` and not a number. The reason why it is reported
as `-` is that the current capacity of the old
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
On Wed, 3 May 2023 21:08:39 GMT, Stefan Karlsson wrote:
>> test/jdk/ProblemList-generational-zgc.txt line 27:
>>
>>> 25: #
>>> 26: # List of quarantined tests for testing with Generational ZGC.
>>> 27: #
>>
>> Are the tests in `test/j
On Thu, 4 May 2023 09:52:25 GMT, Thomas Schatzl wrote:
> Is it possible to remove the G1 hack in this change too? Because since now a
> zero value is supported in the output, there does not seem to be a reason to
> keep it for G1.
I prefer if that is done and tested as a separate PR.
On Mon, 29 May 2023 10:09:15 GMT, Johan Sjölen wrote:
> A final sweep of Hotspot to remove all re-added NULLs. With only 110 changes
> I'd appreciate if this was considered trivial.
Looks good. Though, I'd prefer if we could slightly tweak the following two
print lines.
On Fri, 2 Jun 2023 02:49:25 GMT, Kelvin Nilsen wrote:
>> OpenJDK Colleagues:
>>
>> Please review this proposed integration of Generational mode for Shenandoah
>> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>>
>> Generational mode of Shenandoah is enabled by adding
>>
On Thu, 19 Jan 2023 17:23:19 GMT, Justin King wrote:
>> Remove abstraction that is a holdover from Solaris. Direct usages of
>> `MmapArrayAllocator` have been switched to normal `malloc`. The
>> justification is that none of the code paths are called from signal
>> handlers, so using `mmap`
On Sun, 4 Jun 2023 11:28:33 GMT, Alan Bateman wrote:
> Thread.sleep has had quite a bit of churn recently to support virtual
> threads, add sleep(Duration), a JFR event, and the change the underlying
> implementation to support sub-millis precision. I think the changes have
> settled down now
On Fri, 26 May 2023 20:46:29 GMT, Kelvin Nilsen wrote:
> OpenJDK Colleagues:
>
> Please review this proposed integration of Generational mode for Shenandoah
> GC under https://bugs.openjdk.org/browse/JDK-8307314.
>
> Generational mode of Shenandoah is enabled by adding
>
On Fri, 16 Jun 2023 11:52:51 GMT, Stefan Karlsson wrote:
> Generational ZGC changed the location where the heap object iterator called
> the visit function. It used to be called when the objects were popped and
> then followed, but it was changed so that the function whe
Generational ZGC changed the location where the heap object iterator called the
visit function. It used to be called when the objects were popped and then
followed, but it was changed so that the function where called immediately when
the objects are marked. This gave the benefit that the
On Fri, 16 Jun 2023 11:41:14 GMT, Axel Boldt-Christmas
wrote:
>> The current implementation for testing generational ZGC with jtreg is
>> implemented with a filter on the mode flag `ZGenerational`. Because of this
>> only environments which set this flag explicitly will run most of the tests.
On Tue, 27 Jun 2023 15:11:34 GMT, Coleen Phillimore wrote:
>> Hm. Maybe this would be ok. Our original idea was to make it T* not T until
>> this cast. I don't know how many other cases there are that I haven't
>> gotten to yet. But it would eliminate a cast, so that's good (unless these
On Tue, 27 Jun 2023 12:41:50 GMT, Coleen Phillimore wrote:
> This is another version of PR https://github.com/openjdk/jdk/pull/14659 but
> I've added a pointer delta function in globalDefinitions.hpp to use for these
> pointer diff calculations that return int everywhere. If the name is
>
On Fri, 16 Jun 2023 11:52:51 GMT, Stefan Karlsson wrote:
> Generational ZGC changed the location where the heap object iterator called
> the visit function. It used to be called when the objects were popped and
> then followed, but it was changed so that the function whe
On Fri, 16 Jun 2023 11:52:51 GMT, Stefan Karlsson wrote:
> Generational ZGC changed the location where the heap object iterator called
> the visit function. It used to be called when the objects were popped and
> then followed, but it was changed so that the function whe
On Mon, 8 May 2023 10:19:44 GMT, Fei Yang wrote:
>> Could you provide the values for `reserved`, `ZAddressHeapBase`, and
>> `ZAddressOffsetMax`, when this test is failing. I'd like to know if we can
>> make a workaround for you, or if we have to turn off the test for riscv.
>
> @stefank : I
On Thu, 4 May 2023 09:33:49 GMT, Stefan Karlsson wrote:
> When running jstat tests like the following:
> test/jdk/sun/tools/jstatd/TestJstatdServer.java
>
> with Generational ZGC we get a failure because the O (old generation
> percentage) is reported as `-` and not a number.
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
&g
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
&
On Tue, 9 May 2023 00:50:56 GMT, Fei Yang wrote:
>> That's unfortunate. Could you try this patch, which probes the address range
>> to see if it can reserve the memory somewhere else within
>> `[ZAddressHeapBase, ZAddressHeapBase+ZAddressOffsetMax)`:
>>
to
> mash the two implementations together and sprinkle the GC code with
> conditional statements or dynamic dispatches. We have done similar
> experiments before. When ZGC was first born, we started an experiment where
> we converted G1 into getting the same features as the evolving ZG
to
> mash the two implementations together and sprinkle the GC code with
> conditional statements or dynamic dispatches. We have done similar
> experiments before. When ZGC was first born, we started an experiment where
> we converted G1 into getting the same features as the evolving ZG
On Wed, 3 May 2023 09:04:50 GMT, Stefan Karlsson wrote:
> Hi all,
>
> Please review the implementation of Generational ZGC, which can be turned on
> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
> ZGC is a major rewrite of the non-generatio
On Thu, 11 May 2023 12:12:56 GMT, Stefan Karlsson wrote:
>> Hi all,
>>
>> Please review the implementation of Generational ZGC, which can be turned on
>> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
>> ZGC is a major rewrite of th
On Wed, 3 May 2023 12:29:15 GMT, Martin Doerr wrote:
> Thanks for fixing PPC64! With this, the VM compiles and the
> `test/hotspot/jtreg/gc` tests are passing on linux PPC64le.
>
> I'm glad to see this PR for JDK 21 LTS. It's a big step forward for ZGC.
> Congratulations!
Thanks for porting
Hi all,
Please review the implementation of Generational ZGC, which can be turned on by
adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational ZGC is
a major rewrite of the non-generational ZGC version that exists in the
openjdk/jdk repository. It splits the heap into two
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
&
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC throug
On Thu, 4 May 2023 20:21:12 GMT, Andrey Turbanov wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> undefine glibc major/minor macros
>
> test/hotspot/jtreg/runtime/stringtable/Str
On Fri, 5 May 2023 01:54:48 GMT, Fei Yang wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> undefine glibc major/minor macros
>
> test/hotspot/gtest/gc/z/test_zForwarding.cpp line
On Fri, 5 May 2023 06:28:59 GMT, Yadong Wang wrote:
>> Thanks for reporting. It would be interesting to see what address you get
>> and compare it to the range [ZAddressHeapBase,
>> ZAddressHeapBase+ZAddressOffsetMax).
>
> We emailed to erik to discuss this issue two months ago, and maybe he
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
&g
There have been many contributors of this patch over the years. I'll do my
> best to poke Skara into listing you all, but if you see that I've missed your
> name please reach out to me and I'll fix it.
>
> Testing: we have been continuously running Generational ZGC through Oracle's
&g
1 - 100 of 197 matches
Mail list logo
