nginx.git/src/event, branch release-1.1.8

Silently ignoring a stale global SSL error left after disabled renegotiation.

2011-10-31T14:30:03+00:00

Event pipe: reduced number of file buffers used.

2011-10-31T09:54:55+00:00

If possible we now just extend already present file buffer in p->out chain
instead of keeping ngx_buf_t for each buffer we've flushed to disk.  This
saves about 120 bytes of memory per buffer flushed to disk, and resolves
high CPU usage observed in edge cases (due to coalescing these buffers on
send).

Event pipe: fixes for complex protocols.

2011-10-31T09:53:16+00:00

1. In ngx_event_pipe_write_chain_to_temp_file() make sure to fully write
   all shadow buffers up to last_shadow.  With this change recycled buffers
   cannot appear in p->out anymore.  This also fixes segmentation faults
   observed due to ngx_event_pipe_write_chain_to_temp() not freeing any
   raw buffers while still returning NGX_OK.

2. In ngx_event_pipe_write_to_downstream() we now properly check for busy
   size as a size of buffers, not a size of data in these buffers.  This
   fixes situations where all available buffers became busy (including
   segmentation faults due to this).

3. The ngx_event_pipe_free_shadow_raw_buf() function is dropped.  It's
   incorrect and not needed.

Decrease of log level of some SSL handshake errors.

2011-10-25T15:04:09+00:00

Releasing memory of idle SSL connection. This saves about 34K per SSL

2011-10-07T12:15:20+00:00

connection. The SSL_MODE_RELEASE_BUFFERS option is available since
OpenSSL 1.0.0d.

Disabling SSL compression. This saves about 300K per SSL connection.

2011-10-07T10:59:02+00:00

The SSL_OP_NO_COMPRESSION option is available since OpenSSL 1.0.0.

Fixed loss of chain links in ngx_event_pipe_read_upstream().

2011-09-20T09:56:35+00:00

Fix of cpu hog in event pipe.

2011-09-20T09:55:27+00:00

If client closed connection in ngx_event_pipe_write_to_downstream(), buffers
in the "out" chain were lost.  This caused cpu hog if all available buffers
were in the "out" chain.  Fix is to call ngx_chain_update_chains() before
checking return code of output filter to avoid loosing buffers in the "out"
chain.

Note that this situation (all available buffers in the "out" chain) isn't
normal, it should be prevented by busy buffers limit.  Though right now it
may happen with complex protocols like fastcgi.  This should be addressed
separately.

The "worker_aio_requests" directive.

2011-09-20T07:30:09+00:00

The default value is 32 AIO simultaneous requests per worker. Previously
they were hardcoded to 1024, and it was too large, since Linux allocated
them early on io_setup(), but not on request itself. So with default value
of /proc/sys/fs/aio-max-nr equal to 65536 only 64 worker processes could
be run simultaneously. 32 AIO requests are enough for modern disks even if
server runs only 1 worker.

Replaced "can not" with "cannot" and "could not" in a bunch of places.

2011-09-19T14:48:29+00:00

Fixed nearby grammar errors.