Re: Switch Table Extension for PHP
| From: | Stefan Esser | Date: | Fri, 01 Aug 2008 13:11:32 +0000 |
| Subject: | Re: Switch Table Extension for PHP | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-39540@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Dmitry,
> As you set the extended_value in shared memory to point into process
> memory the other process will read it and look into it's own memory, and
> of course it won't find proper switch-table there.
In case the opcode cache directly uses op_array mapped in shared memory
the extension should result in a slow down because every . However it
SHOULD detect that the extended_value points to an invalid memory
address, because it checks if it points into the memory allocated. The
heap should be random enough to catch this most of the time.
But yeah I know that there are some (potential) problems ;) That is why
it is experimental. The bigger question is however if the whole idea
fails with some switch() constructs.
Stefan Esser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiTC4QACgkQSuF5XhWr2ni66ACdG2DuhO/q2n1StRU559QCPoMn
iiwAoLpBBcA/jQD0NjBajkD/uRpEWa5M
=kloR
-----END PGP SIGNATURE-----