aboutsummaryrefslogtreecommitdiff
path: root/src/os/win32/ngx_shmem.h
Commit message (Collapse)AuthorAge
* Win32: shared memory base addresses and remapping.Maxim Dounin2015-04-27
| | | | | | | | | | | | | | | | | | | | | Two mechanisms are implemented to make it possible to store pointers in shared memory on Windows, in particular on Windows Vista and later versions with ASLR: - The ngx_shm_remap() function added to allow remapping of a shared memory zone to the address originally used for it in the master process. While important, it doesn't solve the problem by itself as in many cases it's not possible to use the address because of conflicts with other allocations. - We now create mappings at the same address in all processes by starting mappings at predefined addresses normally unused by newborn processes. These two mechanisms combined allow to use shared memory on Windows almost without problems, including reloads. Based on the patch by Sergey Brester: http://mailman.nginx.org/pipermail/nginx-devel/2015-April/006836.html
* Copyright updated.Maxim Konovalov2012-01-18
|
* support attaching to an existent Win32 shared memoryIgor Sysoev2009-04-18
|
* move zone name from ngx_shm_zone_t to ngx_shm_t to use Win32 shared memoryIgor Sysoev2009-04-16
|
* fix header name changeIgor Sysoev2006-09-15
|
* nginx-0.3.24-RELEASE importrelease-0.3.24Igor Sysoev2006-02-01
*) Workaround: for bug in FreeBSD kqueue. *) Bugfix: now a response generated by the "post_action" directive is not transferred to a client. *) Bugfix: the memory leaks were occurring if many log files were used. *) Bugfix: the first "proxy_redirect" directive was working inside one location. *) Bugfix: on 64-bit platforms segmentation fault may occurred on start if the many names were used in the "server_name" directives; the bug had appeared in 0.3.18.