|
1 | 1 | /*
|
2 |
| - * Copyright (c) 2005, 2020, Oracle and/or its affiliates. All rights reserved. |
3 |
| - * Copyright (c) 2012, 2018 SAP SE. All rights reserved. |
| 2 | + * Copyright (c) 2005, 2024, Oracle and/or its affiliates. All rights reserved. |
| 3 | + * Copyright (c) 2012, 2024 SAP SE. All rights reserved. |
4 | 4 | * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
|
5 | 5 | *
|
6 | 6 | * This code is free software; you can redistribute it and/or modify it
|
|
49 | 49 | "Allow VM to run with EXTSHM=ON.") \
|
50 | 50 | \
|
51 | 51 | /* Maximum expected size of the data segment. That correlates with the */ \
|
52 |
| - /* to the maximum C Heap consumption we expect. */ \ |
53 |
| - /* We need to know this because we need to leave "breathing space" for the */ \ |
54 |
| - /* data segment when placing the java heap. If that space is too small, we */ \ |
55 |
| - /* reduce our chance of getting a low heap address (needed for compressed */ \ |
56 |
| - /* Oops). */ \ |
| 52 | + /* maximum C Heap consumption we expect. */ \ |
| 53 | + /* We need to leave "breathing space" for the data segment when */ \ |
| 54 | + /* placing the java heap. If the MaxExpectedDataSegmentSize setting */ \ |
| 55 | + /* is too small, we might run into resource issues creating many native */ \ |
| 56 | + /* threads, if it is too large, we reduce our chance of getting a low heap */ \ |
| 57 | + /* address (needed for compressed Oops). */ \ |
57 | 58 | product(uintx, MaxExpectedDataSegmentSize, 8*G, \
|
58 | 59 | "Maximum expected Data Segment Size.") \
|
59 | 60 | \
|
|
0 commit comments