Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88194
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
To: "'Dmitry Stogov'" <dmitry@zend.com>
Cc: "'Anatol Belski'" <ab@php.net>,
	"'Kalle Sommer Nielsen'" <kalle@php.net>,
	"'Rasmus Lerdorf'" <rasmus@lerdorf.com>,
	"'Xinchen Hui'" <xinchen.h@zend.com>,
	"'Nikita Popov'" <nikita.ppv@gmail.com>,
	"'Zeev Suraski'" <zeev@zend.com>,
	"'Andi Gutmans'" <andi@zend.com>,
	"'PHP Internals'" <internals@lists.php.net>
References: <031201d0ef28$abcec710$036c5530$@belski.net> <CA+9eiLtVTwh7eLfb4ynO+BxuvG6jiDnagdEgsv1N=q4_mqGacQ@mail.gmail.com>
In-Reply-To: <CA+9eiLtVTwh7eLfb4ynO+BxuvG6jiDnagdEgsv1N=q4_mqGacQ@mail.gmail.com>
Date: Mon, 14 Sep 2015 23:13:52 +0200
Message-ID: <035401d0ef32$440361e0$cc0a25a0$@belski.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHGC28vWAWs0Pbo/VmQmtRK5zDXJQFxa/PDnka7UbA=
Content-Language: en-us
Subject: RE: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS should be configured to provide huge pages. It's possibl
From: anatol.php@belski.net ("Anatol Belski")



> -----Original Message-----
> From: Dmitry Stogov [mailto:dmitry@zend.com]
> Sent: Monday, September 14, 2015 10:37 PM
> To: Anatol Belski <anatol.php@belski.net>
> Cc: Anatol Belski <ab@php.net>; Kalle Sommer Nielsen <kalle@php.net>;
> Rasmus Lerdorf <rasmus@lerdorf.com>; Xinchen Hui <xinchen.h@zend.com>;
> Nikita Popov <nikita.ppv@gmail.com>; Zeev Suraski <zeev@zend.com>; =
Andi
> Gutmans <andi@zend.com>; PHP Internals <internals@lists.php.net>
> Subject: Re: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an =
experemental
> ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP
> should be configured and built with --enable-huge-code-pages, OS =
should be
> configured to provide huge pages. It's possibl
>=20
> >
> > With the new huge memory pages feature I'd suggest a bit softer -
> > enabling its building, but setting =
opcache.enable_huge_code_pages=3D0 by
> default.
>=20
>=20
> OK.
>=20
>=20
> > Then it can be easy enable and give one more intermediate step for =
pre
> > testing and go into RC4 completely if ok.
>=20
>=20
> In general we may get build problems on some platforms...
>=20
>=20
> > What do you think?
> >
>=20
> I didn't get, do you like to delay this for RC4? or enable it at =
compile time and
> disable at run-time by default for RC3?
> I agree with both.
>=20
I was suggesting the latter - build and disable at run-time. With RC4 I =
meant - as it's run-time enabled by default currently, that could be =
turned on by default in RC4 if everything was well in RC3.

Regarding possible build issues you mention - probably some magic in =
config.m4 could disable huge pages? I wasn't aware, but probably yep - =
like FreeBSD or OSX likely to not to have the sys/prctl.h . This could =
be a reason for delaying till RC4, but it's actually easy solved doing =
some test compilation in config.m4 . I'd see build + disable on run-time =
in RC3 as a better move because it turns the test circle earlier which =
is good considering there are only 4 RCs to go yet.

Regards

Anatol