Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88591
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+9eiLtwyayxzbTT+0Fi7JnB9WPc7SkUFH+r3vOW49bdjRCUJw@mail.gmail.com>
References: <CAMbn9ZEHXT7SPCo1ai4FpVfjR7X+vPe+uEOKwY13VDdJR4g6+g@mail.gmail.com>
	<CA+9eiLsu2K9v-89w8RbHvyd=yH+Nu_tQLnzucRWhr1CzdhGciA@mail.gmail.com>
	<CAMbn9ZEKG0c=xaDiN5hzxC2H+rvL2pszUh3-+D+n+QXvopejbQ@mail.gmail.com>
	<CA+9eiLtHFFXFqOA18VJGKULgqHqjx=krPWQxBrSnb-V2MogQ1w@mail.gmail.com>
	<CA+9eiLt=qF8yy0rPYqUH3ZdrNRUvkCo94gbR685SB5NRD2wacQ@mail.gmail.com>
	<CAMbn9ZHcZ3FZHyGDKMwjAWBKW4Wum84q9ShUJ+ES8eqaK+Oyvw@mail.gmail.com>
	<CA+9eiLtwyayxzbTT+0Fi7JnB9WPc7SkUFH+r3vOW49bdjRCUJw@mail.gmail.com>
Date: Thu, 1 Oct 2015 13:25:28 +0700
Message-ID: <CAEZPtU5YKUOeNT0G3=8fyy3g0Fug1ZpMkSE_th35YKM9azamEA@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Anatoliy Belsky <ab@php.net>, Laruence <laruence@php.net>, 
	PHP Internals <internals@lists.php.net>, "dmitry@php.net" <dmitry@php.net>, 
	Matt Ficken <themattficken@gmail.com>
Content-Type: multipart/alternative; boundary=001a113cf4f014f3cd0521051dba
Subject: Re: [PHP-DEV] Re: Windows OpCache bug fix
From: pierre.php@gmail.com (Pierre Joye)

--001a113cf4f014f3cd0521051dba
Content-Type: text/plain; charset=UTF-8

On Oct 1, 2015 3:59 AM, "Dmitry Stogov" <dmitry@zend.com> wrote:
>
> Hi Matt,
>
> Thanks for looking into the problem, but I afraid that the proposed
> solution won't solve the problem completely, but may introduce new
> problems. At first, we might to reserve N times more memory. Then
different
> SHM segments might contain different data. opcache_reset(),
> opcache_invalidate() and others will affect only one segment.
>
> I think the perfect solution would require converting all stored data in
> position independent format, but this hardly ever is going to be done even
> for php-8.
>
> We may fallback to use file-cache introduced in php-7. (this should work
> out of the box or with minimal changes).
>
> Also. if we can't map SHM into desired address space, we may map it in any
> other address and copy data into the process memory similar to file-cache.

And what wincache does. It is slower but the request is served.

> Finally we may try to use /DYNAMICBASE:NO

--001a113cf4f014f3cd0521051dba--