Req #14208 [Com]: shm_put_var problem and new shm functions

Edit report at https://bugs.php.net/bug.php?id=14208&edit=1 ID: 14208 Comment by: sample at email dot tst Reported by: duncan at emarketeers dot com Summary: shm_put_var problem and new shm functions Status: Analyzed Type: Feature/Change Request Package: Semaphore related Operating System: All PHP Version: 4.0.6 Block user comment: N Private report: N New Comment: 555 Previous Comments: ------------------------------------------------------------------------ [2020-08-28 15:34:24] sample at email dot tst The following patch has been added/updated: Patch Name: mulOMpUR Revision: 1598628864 URL: https://bugs.php.net/patch-display.php?bug=14208&patch=mulOMpUR&revision=1598628864 ------------------------------------------------------------------------ [2003-05-31 10:32:48] andrey@php.net Assigning to Wez since he implemented sysvmsg. Hopefully he will review the patch ;) ------------------------------------------------------------------------ [2003-01-20 11:49:10] iliaa@php.net Please send further patches in unified format, it makes it much easier to read :) ------------------------------------------------------------------------ [2003-01-20 10:18:06] andrey@php.net The mail from Duncan : It makes updates twice as fast. My LRU code is knocking around somewhere, but I'll have to do some rummaging if you want it. 367c367,376 < php_remove_shm_data(ptr, shm_varpos); --- > shm_var = (sysvshm_chunk*)((char*)ptr + shm_varpos); > /* Check the new length against the old length */ > if(shm_var->length != len ) { > /* If not equal, remove the old entry and prepare to create a new one */ > php_remove_shm_data(ptr, shm_varpos); > } else { > /* If equal, just copy the new data across and return */ > memcpy(&(shm_var->mem),data,len); > return 0; > } ------------------------------------------------------------------------ [2003-01-18 12:53:21] andrey@php.net Where is the patch? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=14208 -- Edit this bug report at https://bugs.php.net/bug.php?id=14208&edit=1