jmx-dev RFR 6425769: jmx remote bind address

2015-11-02 Thread Severin Gehwolf
Hi, Here is a patch addressing JDK-6425769. The issue is that the JMX agent binds to the wildcard address by default, preventing users to use system properties for JMX agents on multi-homed hosts. Given a host with local network interfaces, 192.168.0.1 and 192.168.0.2 say, it's impossible to start

Re: jmx-dev RFR 6425769: jmx remote bind address

2015-11-02 Thread Severin Gehwolf
> changing the existing one (adding SslRmiServerSocketFactory public > constructors) so compatibility review process will have to be > involved. OK. What exactly is there for me to do? I'm not familiar with this process. Note that the intent would be to get this backported

Re: jmx-dev RFR 6425769: jmx remote bind address

2015-11-04 Thread Severin Gehwolf
oking for a sponsor and a hotspot/servicability-dev reviewer. Could somebody maintaining javax.rmi.ssl have a look at this as well? Thank you! Cheers, Severin On Tue, 2015-11-03 at 15:45 +0100, Jaroslav Bachorik wrote: > On 2.11.2015 19:06, Severin Gehwolf wrote: > > Hi, > > >

Re: jmx-dev RFR 6425769: jmx remote bind address

2015-11-09 Thread Severin Gehwolf
On Wed, 2015-11-04 at 11:54 +0100, Severin Gehwolf wrote: > Hi, > > Updated webrev with jtreg test in Java: > http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/02/ > bug: https://bugs.openjdk.java.net/browse/JDK-6425769 > > I believe this updated webrev addre

Re: jmx-dev RFR 6425769: jmx remote bind address

2015-11-18 Thread Severin Gehwolf
k.java.net/browse/JDK-6425769 webrev:  http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/03.no-rmi-ssl-factory-changes/ Thanks, Severin On Mon, 2015-11-09 at 10:32 +0100, Severin Gehwolf wrote: > On Wed, 2015-11-04 at 11:54 +0100, Severin Gehwolf wrote: > > Hi, > > > > Up

Re: jmx-dev [PING] RFR 6425769: jmx remote bind address

2015-12-01 Thread Severin Gehwolf
On Mon, 2015-11-09 at 10:32 +0100, Severin Gehwolf wrote: > On Wed, 2015-11-04 at 11:54 +0100, Severin Gehwolf wrote: > > Hi, > > > > Updated webrev with jtreg test in Java: > > http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-6425769/02/ > > bug: https://bugs.op

Re: jmx-dev [PING] RFR 6425769: jmx remote bind address

2015-12-01 Thread Severin Gehwolf
Hi Jaroslav, On Tue, 2015-12-01 at 12:33 +0100, Jaroslav Bachorik wrote: > On 1.12.2015 11:17, Severin Gehwolf wrote: > > On Mon, 2015-11-09 at 10:32 +0100, Severin Gehwolf wrote: > > > On Wed, 2015-11-04 at 11:54 +0100, Severin Gehwolf wrote: > > > > Hi, > &

Re: jmx-dev [PING-2] RFR 6425769: jmx remote bind address

2015-12-09 Thread Severin Gehwolf
On Tue, 2015-12-01 at 14:19 +0100, Severin Gehwolf wrote: > Hi Jaroslav, > > On Tue, 2015-12-01 at 12:33 +0100, Jaroslav Bachorik wrote: > > On 1.12.2015 11:17, Severin Gehwolf wrote: > > > On Mon, 2015-11-09 at 10:32 +0100, Severin Gehwolf wrote: > > > &g

Re: jmx-dev [PING-2] RFR 6425769: jmx remote bind address

2015-12-09 Thread Severin Gehwolf
On Wed, 2015-12-09 at 14:58 +0100, Jaroslav Bachorik wrote: > On 9.12.2015 14:55, Severin Gehwolf wrote: > > On Tue, 2015-12-01 at 14:19 +0100, Severin Gehwolf wrote: > > > Hi Jaroslav, > > > > > > On Tue, 2015-12-01 at 12:33 +0100, Jaroslav Bachorik wrote:

Re: jmx-dev RFR 8145982: JMXInterfaceBindingTest is failing intermittently

2015-12-22 Thread Severin Gehwolf
On Tue, 2015-12-22 at 17:50 +0100, Jaroslav Bachorik wrote: > Please, review this trivial test change > > Issue : https://bugs.openjdk.java.net/browse/JDK-8145982 > Webrev: http://cr.openjdk.java.net/~jbachorik/8145982/webrev.00 > > The test calls System.exit(0) in case when it is not applicable

Re: jmx-dev [ding] Re: [pong] Re: [ping] Re: RFR 8146015: JMXInterfaceBindingTest is failing intermittently for IPv6 addresses

2016-01-14 Thread Severin Gehwolf
Hi, On Wed, 2016-01-13 at 10:51 -0800, serguei.spit...@oracle.com wrote: > On 1/13/16 03:16, Jaroslav Bachorik wrote: > > On 12.1.2016 12:55, serguei.spit...@oracle.com wrote: > > > On 1/12/16 03:49, Jaroslav Bachorik wrote: > > > > On 12.1.2016 11:47, serguei.spit...@oracle.com wrote: > > > > > O

Re: jmx-dev [ding] Re: [pong] Re: [ping] Re: RFR 8146015: JMXInterfaceBindingTest is failing intermittently for IPv6 addresses

2016-01-15 Thread Severin Gehwolf
Hi, On Fri, 2016-01-15 at 09:50 +0100, Jaroslav Bachorik wrote: > > Sorry for being late in the game with this. > > > > +private static List getAddressesForLocalHost() { > > + > >   try { > > -addrs = InetAddress.getAllByName("localhost"); > > -} catch (UnknownHost

Re: jmx-dev [ding] Re: [pong] Re: [ping] Re: RFR 8146015: JMXInterfaceBindingTest is failing intermittently for IPv6 addresses

2016-01-15 Thread Severin Gehwolf
On Fri, 2016-01-15 at 10:28 +0100, Jaroslav Bachorik wrote: > On 15.1.2016 10:24, Severin Gehwolf wrote: > > Hi, > > > > On Fri, 2016-01-15 at 09:50 +0100, Jaroslav Bachorik wrote: > > > > Sorry for being late in the game with this. > >

jmx-dev [8] RFR(S): 8147857: RMIConnector logs attribute names incorrectly

2016-01-21 Thread Severin Gehwolf
Hi, Could somebody please review and sponsor this small 8u bugfix? This bug has been introduced with the January 2016 CPU fixes (JDK-8130710) and I've not seen this code in JDK 9 (yet?). Hence, posting this here. Bug: https://bugs.openjdk.java.net/browse/JDK-8147857 webrev: http://cr.openjdk.java

Re: jmx-dev [8] RFR(S): 8147857: RMIConnector logs attribute names incorrectly

2016-01-21 Thread Severin Gehwolf
Thanks, Jaroslav. Any JDK 8 reviewer willing to have a look at this? Thanks, Severin On Thu, 2016-01-21 at 12:01 +0100, Jaroslav Bachorik wrote: > On 21.1.2016 11:30, Severin Gehwolf wrote: > > Hi, > > > > Could somebody please review and sponsor this small 8u bugfix?

Re: jmx-dev [8] RFR(S): 8147857: RMIConnector logs attribute names incorrectly

2016-01-22 Thread Severin Gehwolf
On Thu, 2016-01-21 at 18:03 +0100, Daniel Fuchs wrote: > On 21/01/16 15:20, Severin Gehwolf wrote: > > Thanks, Jaroslav. Any JDK 8 reviewer willing to have a look at this? > > Looks good to me Severin. Thank you, Daniel! Cheers, Severin > best regards, > > -

Re: jmx-dev 8221303: sun/management/jmxremote/bootstrap/JMXInterfaceBindingTest.java fails due to java.rmi.server.ExportException: Port already in use

2019-07-18 Thread Severin Gehwolf
Hi Daniil, On Wed, 2019-07-17 at 18:26 -0700, Daniil Titov wrote: > Hi Chris, > > Yes, I added output.reportDiagnosticSummary() in webrev-01, but removed it > In webrev-02, and later restored it in webrev-03. > > When the test runs of retries output.getExitValue() is set to 1 > (COMMUNICATION_

Re: jmx-dev 8226575: OperatingSystemMXBean should be made container aware

2019-12-04 Thread Severin Gehwolf
On Wed, 2019-12-04 at 08:32 -0500, Bob Vandette wrote: > You can try to use containerMetrics.getPerCpuUsage() instead of > containerMetrics.getEffectiveCpuSetCpus(). > The length of the array returned is the number of host cpus. Maybe Severin > can confirm if this true in cgroupv2 as > well. If

jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo

2021-01-18 Thread Severin Gehwolf
This patch adds some explicit capacity for local refs. New regression test fails prior and passes after the patch. Thoughts? - Commit messages: - 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo Changes: https://git.openjdk.java.net/jdk/pull/2130/files Webrev: http

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v2]

2021-01-19 Thread Severin Gehwolf
On Mon, 18 Jan 2021 23:06:07 GMT, David Holmes wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contai

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v2]

2021-01-19 Thread Severin Gehwolf
> This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Severin Gehwolf has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v2]

2021-01-19 Thread Severin Gehwolf
On Tue, 19 Jan 2021 09:41:27 GMT, Aleksey Shipilev wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contai

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo

2021-01-19 Thread Severin Gehwolf
On Mon, 18 Jan 2021 14:10:56 GMT, Severin Gehwolf wrote: > This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Thanks for the review! More thoughts? - PR: https://git.openjdk.java.net/jdk/pull/2130

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v3]

2021-01-20 Thread Severin Gehwolf
> This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Severin Gehwolf has updated the pull request incrementally with one additional commit since the last revision: Actually assign the variable r

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v4]

2021-01-20 Thread Severin Gehwolf
> This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Severin Gehwolf has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v2]

2021-01-20 Thread Severin Gehwolf
On Tue, 19 Jan 2021 19:55:22 GMT, Chris Plummer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contai

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v5]

2021-01-21 Thread Severin Gehwolf
> This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Severin Gehwolf has updated the pull request incrementally with two additional commits since the last revision: - Improve popping of local frames

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v4]

2021-01-21 Thread Severin Gehwolf
On Thu, 21 Jan 2021 09:06:00 GMT, Aleksey Shipilev wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request conta

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v4]

2021-01-21 Thread Severin Gehwolf
On Wed, 20 Jan 2021 21:20:43 GMT, Chris Plummer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request conta

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v5]

2021-01-22 Thread Severin Gehwolf
On Thu, 21 Jan 2021 20:46:12 GMT, Chris Plummer wrote: > Getting close: > > * Line 188 where there is a JNU_ThrowOutOfMemoryError needs a > PopLocalFrame before it. > * Copyrights need updating Should be fixed now. Thoughts? - PR: https://git.openjdk.java.net/jdk/pull/213

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v6]

2021-01-22 Thread Severin Gehwolf
> This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? Severin Gehwolf has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v5]

2021-01-22 Thread Severin Gehwolf
On Thu, 21 Jan 2021 20:46:12 GMT, Chris Plummer wrote: >> Severin Gehwolf has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Improve popping of local frames in the error case >> - Make HOTSPOT_DIAGNOSTIC

Re: jmx-dev RFR: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo [v6]

2021-01-25 Thread Severin Gehwolf
On Fri, 22 Jan 2021 20:18:39 GMT, Chris Plummer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request cont

jmx-dev Integrated: 8258836: JNI local refs exceed capacity getDiagnosticCommandInfo

2021-01-25 Thread Severin Gehwolf
On Mon, 18 Jan 2021 14:10:56 GMT, Severin Gehwolf wrote: > This patch adds some explicit capacity for local refs. New regression test > fails prior and passes after the patch. > > Thoughts? This pull request has now been integrated. Changeset: af155fc0 Author:Severin

Re: jmx-dev RFR: 8265104: CpuLoad and SystemCpuLoad in OperatingSystem MXBean returns -1.0 [v2]

2021-04-13 Thread Severin Gehwolf
On Tue, 13 Apr 2021 06:55:20 GMT, Yasumasa Suenaga wrote: >> I got -1.0 from both CpuLoad and SystemCpuLoad in OperatingSystem MXBean >> when I run the application on Fedora 33 x64 which is installed cgroups V2. >> >> ![jconsole-cpuload](https://user-images.githubusercontent.com/7421132/1144857

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load

2021-05-06 Thread Severin Gehwolf
On Thu, 6 May 2021 02:34:01 GMT, Hao Tang wrote: >> Thanks for linking that. It sounds reasonable to me to prefer `quota` in >> that case. > >> Thanks for linking that. It sounds reasonable to me to prefer `quota` in >> that case. > > Yes, flag `PreferContainerQuotaForCPUCount` is [true by >

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load

2021-05-06 Thread Severin Gehwolf
On Fri, 23 Apr 2021 13:33:42 GMT, Hao Tang wrote: > OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though > the CPU load is obviously below 100%. > > We created a 5-core container and run 4 "while (true)" loops in the > container. OperatingSystemImpl.getCpuLoad() returne

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load

2021-05-06 Thread Severin Gehwolf
On Thu, 6 May 2021 12:36:09 GMT, Severin Gehwolf wrote: >>> Thanks for linking that. It sounds reasonable to me to prefer `quota` in >>> that case. >> >> Yes, flag `PreferContainerQuotaForCPUCount` is [true by >> default](https://github.com/openjdk/jd

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load

2021-05-06 Thread Severin Gehwolf
On Thu, 6 May 2021 16:31:57 GMT, Argha C wrote: >> Thanks for linking that. It sounds reasonable to me to prefer `quota` in >> that case. > >> @argha-c The proposed fix is within the `quota > 0` condition. I.e. this is >> code only run when CPU quotas, _not_ shares are in effect. In docker/pod

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v2]

2021-05-21 Thread Severin Gehwolf
On Tue, 11 May 2021 14:57:32 GMT, Hao Tang wrote: >> OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though >> the CPU load is obviously below 100%. >> >> We created a 5-core container and run 4 "while (true)" loops in the >> container. OperatingSystemImpl.getCpuLoad() re

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v2]

2021-05-21 Thread Severin Gehwolf
On Tue, 11 May 2021 15:48:43 GMT, Hao Tang wrote: >>> Thanks for linking that. It sounds reasonable to me to prefer `quota` in >>> that case. >> >> Yes, flag `PreferContainerQuotaForCPUCount` is [true by >> default](https://github.com/openjdk/jdk/blob/739769c8/src/hotspot/os/linux/globals_lin

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v4]

2021-05-25 Thread Severin Gehwolf
On Tue, 25 May 2021 06:25:23 GMT, Hao Tang wrote: >> OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though >> the CPU load is obviously below 100%. >> >> We created a 5-core container and run 4 "while (true)" loops in the >> container. OperatingSystemImpl.getCpuLoad() re

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v4]

2021-05-25 Thread Severin Gehwolf
On Tue, 25 May 2021 06:25:23 GMT, Hao Tang wrote: >> OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though >> the CPU load is obviously below 100%. >> >> We created a 5-core container and run 4 "while (true)" loops in the >> container. OperatingSystemImpl.getCpuLoad() re

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v4]

2021-05-26 Thread Severin Gehwolf
On Tue, 25 May 2021 09:53:02 GMT, Severin Gehwolf wrote: >> Hao Tang has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Fix compile errors on MacOS > > Bumping number of required reviewers to 2 as I'm a c

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v6]

2021-05-26 Thread Severin Gehwolf
On Tue, 25 May 2021 21:46:27 GMT, Hao Tang wrote: >> OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though >> the CPU load is obviously below 100%. >> >> We created a 5-core container and run 4 "while (true)" loops in the >> container. OperatingSystemImpl.getCpuLoad() re

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v6]

2021-05-26 Thread Severin Gehwolf
On Tue, 25 May 2021 21:46:27 GMT, Hao Tang wrote: >> OperatingSystemImpl.getCpuLoad() may return 1.0 in a container, even though >> the CPU load is obviously below 100%. >> >> We created a 5-core container and run 4 "while (true)" loops in the >> container. OperatingSystemImpl.getCpuLoad() re

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v6]

2021-05-27 Thread Severin Gehwolf
On Thu, 27 May 2021 00:47:23 GMT, Yasumasa Suenaga wrote: > I haven't followed yet all of discussions in this review, but I concern this > PR changes the meaning of `getCpuLoad()`. Does it? Here is the javadoc: https://docs.oracle.com/en/java/javase/16/docs/api/jdk.management/com/sun/management

Re: jmx-dev RFR: 8265836: OperatingSystemImpl.getCpuLoad() returns incorrect CPU load inside a container [v6]

2021-05-27 Thread Severin Gehwolf
On Thu, 27 May 2021 08:37:11 GMT, Hao Tang wrote: >> I haven't followed yet all of discussions in this review, but I concern this >> PR changes the meaning of `getCpuLoad()`. >> >> `getCpuLoad()` has been based on total time since the start of the >> container, but after this PR, it is based

jmx-dev RFR: 8268103: JNI functions incorrectly return a double after JDK-8265836

2021-06-02 Thread Severin Gehwolf
Please review this trivial patch. Stubs should return `-1` for `jlong` rather than `-1.0` (`double`) on aix/macosx. Thoughts? - Commit messages: - 8268103: JNI functions incorrectly return a double after JDK-8265836 Changes: https://git.openjdk.java.net/jdk/pull/4300/files Webre

Re: jmx-dev RFR: 8268103: JNI functions incorrectly return a double after JDK-8265836

2021-06-02 Thread Severin Gehwolf
On Wed, 2 Jun 2021 08:58:06 GMT, Severin Gehwolf wrote: > Please review this trivial patch. Stubs should return `-1` for `jlong` > rather than `-1.0` (`double`) on aix/macosx. > > Thoughts? Thanks for the reviews! - PR: https://git.openjdk.java.net/jdk/pull/4300

jmx-dev Integrated: 8268103: JNI functions incorrectly return a double after JDK-8265836

2021-06-02 Thread Severin Gehwolf
On Wed, 2 Jun 2021 08:58:06 GMT, Severin Gehwolf wrote: > Please review this trivial patch. Stubs should return `-1` for `jlong` > rather than `-1.0` (`double`) on aix/macosx. > > Thoughts? This pull request has now been integrated. Changeset: 2963c9e6 Author:Severin

Re: jmx-dev RFR: 8268361: Fix the infinite loop in next_line

2021-06-08 Thread Severin Gehwolf
On Sun, 6 Jun 2021 14:47:31 GMT, UncleNine wrote: > If the /proc/stat mount point is changed in container environment, the while > loop may lead to 100% cpu usage. In what way have you observed /proc/stat being changed which manifests in 100% cpu usage? - PR: https://git.openjdk

Re: jmx-dev RFR: 8268361: Fix the infinite loop in next_line [v2]

2021-06-09 Thread Severin Gehwolf
On Tue, 8 Jun 2021 16:43:14 GMT, UncleNine wrote: >> In my case, it happened in the container environment. >> the /proc filesystem of the container is provided by lxcfs, but a lxcfs bug >> may make the /proc/stat mount point change, then the file descriptor is >> different and fgetc functio

Re: jmx-dev RFR: 8268361: Fix the infinite loop in next_line [v4]

2021-06-09 Thread Severin Gehwolf
On Wed, 9 Jun 2021 14:45:35 GMT, UncleNine wrote: >> If the /proc/stat mount point is changed in container environment, the while >> loop may lead to 100% cpu usage. > > UncleNine has refreshed the contents of this pull request, and previous > commits have been removed. The incremental views w

Re: jmx-dev RFR: 8268361: Fix the infinite loop in next_line [v5]

2021-06-10 Thread Severin Gehwolf
On Thu, 10 Jun 2021 12:28:37 GMT, UncleNine wrote: >> If the /proc/stat mount point is changed in container environment, the while >> loop may lead to 100% cpu usage. > > UncleNine has refreshed the contents of this pull request, and previous > commits have been removed. The incremental views

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v2]

2021-07-07 Thread Severin Gehwolf
On Wed, 7 Jul 2021 07:55:10 GMT, xpbob wrote: >> …ocess cpu usage in containers > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > remove empty line This patch seems fine in principle, but I don't like the duplication. Right now,

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v2]

2021-07-07 Thread Severin Gehwolf
On Wed, 7 Jul 2021 07:50:51 GMT, Yasumasa Suenaga wrote: > In HotSpot, CPU usage for JVM would be calculated at `get_jvm_tickes()` in > os_perf_linux.cpp . It refers `/proc/self/stat` - should we refer it in same > way? > > I discussed about similar issue in #4299 , then we came to an agreemen

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v2]

2021-07-07 Thread Severin Gehwolf
On Wed, 7 Jul 2021 08:31:22 GMT, Severin Gehwolf wrote: > This patch seems fine in principle [...] Let me revise this. It looks like imposing CPU limits via cpuset-cpus would go down a path which won't have this fixed with the current patch. - PR: https://git.openjdk.java

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v4]

2021-07-09 Thread Severin Gehwolf
On Thu, 8 Jul 2021 02:51:09 GMT, xpbob wrote: >> …ocess cpu usage in containers > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > remove whitespace Thanks for the update. `getProcessCpuLoad()` and `getCpuLoad()` looks way too sim

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v4]

2021-07-12 Thread Severin Gehwolf
On Mon, 12 Jul 2021 03:46:23 GMT, xpbob wrote: > > Thanks for the update. `getProcessCpuLoad()` and `getCpuLoad()` looks way > > too similar to me. Is there a way to make them more generic and do the > > process vs. system paths as needed? I think there is. > > use getCpuLoadWithTarget for pr

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v7]

2021-07-13 Thread Severin Gehwolf
On Tue, 13 Jul 2021 05:19:25 GMT, xpbob wrote: >> …ocess cpu usage in containers > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > Set 1.0 for cpu set max https://github.com/jerboaa/jdk/actions/runs/1026610314 is a pre-integration

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v7]

2021-07-13 Thread Severin Gehwolf
On Tue, 13 Jul 2021 05:19:25 GMT, xpbob wrote: >> …ocess cpu usage in containers > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > Set 1.0 for cpu set max Except for the missing comments in the new code blocks this looks good to m

Re: jmx-dev RFR: 8269851: OperatingSystemMXBean getProcessCpuLoad reports incorrect process cpu usage in containers [v8]

2021-07-14 Thread Severin Gehwolf
On Wed, 14 Jul 2021 04:00:39 GMT, xpbob wrote: >> …ocess cpu usage in containers > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > Add comments Still looks good. - Marked as reviewed by sgehwolf (Reviewer). PR: htt

Re: jmx-dev RFR: 8283903: GetContainerCpuLoad does not return the correct result in share mode [v3]

2022-03-30 Thread Severin Gehwolf
On Wed, 30 Mar 2022 06:20:19 GMT, xpbob wrote: >> ``` >>long hostTicks = getHostTotalCpuTicks0(); >> int totalCPUs = getHostOnlineCpuCount0(); >> int containerCPUs = getAvailableProcessors(); >> // scale the total host load t

Re: jmx-dev RFR: 8283903: GetContainerCpuLoad does not return the correct result in share mode [v3]

2022-03-30 Thread Severin Gehwolf
On Wed, 30 Mar 2022 09:17:03 GMT, Kevin Walls wrote: > Hi, Could the bug description be updated to state what the problem is, and > under what circumstances is there a problem? +1 - PR: https://git.openjdk.java.net/jdk/pull/8028

Re: jmx-dev RFR: 8283903: GetContainerCpuLoad does not return the correct result in share mode [v3]

2022-03-30 Thread Severin Gehwolf
On Wed, 30 Mar 2022 09:49:47 GMT, xpbob wrote: >> src/jdk.management/unix/classes/com/sun/management/internal/OperatingSystemImpl.java >> line 96: >> >>> 94: int containerCPUs = getAvailableProcessors(); >>> 95: // scale the total host load to the actual containe

Re: jmx-dev RFR: 8283903: GetContainerCpuLoad does not return the correct result in share mode [v4]

2022-03-30 Thread Severin Gehwolf
On Wed, 30 Mar 2022 11:02:18 GMT, xpbob wrote: >> ``` >>long hostTicks = getHostTotalCpuTicks0(); >> int totalCPUs = getHostOnlineCpuCount0(); >> int containerCPUs = getAvailableProcessors(); >> // scale the total host load t