Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change control access of isLargePage in MemoryManager to public #4701

Merged
merged 1 commit into from
Jan 10, 2020

Conversation

bragaigor
Copy link
Contributor

@bragaigor bragaigor commented Jan 9, 2020

Change control access of isLargePage in MemoryManager to public

This update is required by eclipse-openj9/openj9#8254
Related to issue: #4703

Signed-off-by: Igor Braga higorb1@gmail.com

@rwy7
Copy link
Contributor

rwy7 commented Jan 9, 2020

@genie-omr build all

@youngar
Copy link
Contributor

youngar commented Jan 9, 2020

@bragaigor Can you update the copyright?

@youngar
Copy link
Contributor

youngar commented Jan 9, 2020

@bragaigor It looks like you rolled in an extra commit, was this an accident?

@bragaigor bragaigor force-pushed the islargepages branch 4 times, most recently from 7472f2f to 25f1a7f Compare January 10, 2020 14:28
@bragaigor
Copy link
Contributor Author

@genie-omr build all

@@ -257,6 +257,7 @@ class MM_GCExtensionsBase : public MM_BaseVirtual {
bool largePageWarnOnError;
bool largePageFailOnError;
bool largePageFailedToSatisfy;
bool isDoubleMapRequested; /** Value of -XXgc:enableDoubleMapping <true> or -XXgc:disableDoubleMapping <false> specified by the user */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should not really refer to option name directly (they are specific for OpenJ9). let alone (in theory) they can be even set by some other means like shell environmental variables, property files etc.

@bragaigor bragaigor changed the title Change control access of isLargePage in MemoryManager to public WIP - Change control access of isLargePage in MemoryManager to public Jan 10, 2020
This update is required by eclipse-openj9/openj9#8254

Signed-off-by: Igor Braga <higorb1@gmail.com>
@bragaigor
Copy link
Contributor Author

@genie-omr build all

@bragaigor bragaigor changed the title WIP - Change control access of isLargePage in MemoryManager to public Change control access of isLargePage in MemoryManager to public Jan 10, 2020
bragaigor added a commit to bragaigor/omr that referenced this pull request Jan 10, 2020
Change control access of isLargePage in MemoryManager to public eclipse-omr#4701

Add arraylet double map request field eclipse-omr#4704

Introduce double mapping verbose GC option for
balanced GC policy where it outputs "true" if arraylet
double mapping is enabled and "false" otherwise eclipse-omr#4705

Signed-off-by: Igor Braga <higorb1@gmail.com>
@youngar youngar merged commit 5c57cb3 into eclipse-omr:master Jan 10, 2020
bragaigor added a commit to bragaigor/openj9 that referenced this pull request Jan 14, 2020
In systems that support huge pages, the heap is created using
the available huge pages (normally 2MB). The path taken to
create a heap with huge pages is different from the one taken
when normal page sizes are used. In order for double map to
work, heap must be created using mmap with a file descriptor
associated with the heap. However, doing that with huge pages
is not supported in early glibc versions; in such versions,
glibc only supports mmap + MAP_HUGETLB with anonymous mapping,
which is the opposite of what we want (with anonymous mapping
we cannot use a file descriptor). For now we disable double
mapping whenever huge pages are used; however in a later
release we optimally want to enable it by using memfd_create(2)
which also returns a file descriptor just like shm_open(3) but
it uses the same semantics as other anonymous memory
allocations unlike shm_open(3).

Introduce double mapping verbose GC option for
balanced GC policy

This PR is dependent of eclipse-omr/omr#4701

Signed-off-by: Igor Braga <higorb1@gmail.com>
@bragaigor bragaigor deleted the islargepages branch January 15, 2020 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants