Thank you Eric! On Wed, Oct 18, 2017 at 1:29 PM, Erik Joelsson <[email protected]> wrote:
> I can sponsor the change. > > /Erik > > On 2017-10-18 12:00, Thomas Stüfe wrote: > > Hi Goetz, Eric, > > I was unable to commit this patch before the jdk10 repo consolidation and > would like to do so now. > > Last Webrev: http://cr.openjdk.java.net/~stuefe/webrevs/ > 8187228-make-data-segment-page-size-64K-by-default/webrev.01/webrev/ > > Nothing changed, the webrev is just rebased to the new repo. > > I am unclear whether I am allowed to push this on my own? Does the build > group this? > > Kind Regards, Thomas > > > On Thu, Sep 7, 2017 at 2:33 PM, Thomas Stüfe <[email protected]> > wrote: > >> Thank you Goetz! >> >> On Thu, Sep 7, 2017 at 2:18 PM, Lindenmaier, Goetz < >> [email protected]> wrote: >> >>> Hi Thomas, >>> >>> Looks good. >>> >>> Best regards, >>> Goetz. >>> >>> > -----Original Message----- >>> > From: ppc-aix-port-dev [mailto:ppc-aix-port-dev- >>> > [email protected]] On Behalf Of Thomas Stüfe >>> > Sent: Donnerstag, 7. September 2017 12:02 >>> > To: [email protected]; build-dev <build- >>> > [email protected]> >>> > Subject: RFR(xs): 8187228: [aix] make data segment page size 64K by >>> default >>> > >>> > Hi all, >>> > >>> > may I please have a review for the following AIX-only patch. >>> > >>> > Issue: >>> > https://bugs.openjdk.java.net/browse/JDK-8187228 >>> > <https://bugs.openjdk.java.net/browse/JDK-8187228> >>> > >>> > >>> > webrev: >>> > http://cr.openjdk.java.net/~stuefe/webrevs/8187228-make-data-segment- >>> > page-size-64K-by-default/webrev.00/webrev/ >>> > <http://cr.openjdk.java.net/~stuefe/webrevs/8187228-make-data- >>> > segment-page-size-64K-by-default/webrev.00/webrev/> >>> > >>> > >>> > It changes the default page size for the data segment (C-heap and Posix >>> > Thread Stacks) to 64K. >>> > >>> > >>> > For completeness and simplicity sake, it also changes default page >>> size for >>> > text segment and primordial thread stacl to 64K, but that does not >>> matter >>> > much. >>> > >>> > For more details, please see the issue description. >>> > >>> > Thank you, Thomas >>> >> >> > >
