Re: Is ink_freelist_new thread safe?

2011-05-25 Thread aniket ray
On Tue, May 24, 2011 at 9:52 PM, Leif Hedstrom wrote: > On 05/24/2011 10:14 AM, aniket ray wrote: >> >> It's trafficserver 2.1.5-unstable > > Can you try v2.1.8, or even better, current trunk, I know we fixed several > bugs related to this code since v2.1.5. > I ported my plugin to the new version

Re: Is ink_freelist_new thread safe?

2011-05-25 Thread John Plevyak
There is no 64MB freelist unless you have created one yourself. The buffer freelists max out at 2MB and unless you are caching files you should not see them allocated. john On Wed, May 25, 2011 at 2:24 AM, aniket ray wrote: > On Tue, May 24, 2011 at 9:52 PM, Leif Hedstrom wrote: > > On 05/24/

Keep-Alive Pool

2011-05-25 Thread mark
From what I've observed, ATS' keepalive/connection cache only indexes by the OS server or next proxy server, but not by other types of connection/transport/socket parameters, specifically in my case, negotiated SOCKS connections and outgoing connections which are bound to a specific source IP

Re: Keep-Alive Pool

2011-05-25 Thread Leif Hedstrom
On 05/25/2011 10:17 AM, mark wrote: From what I've observed, ATS' keepalive/connection cache only indexes by the OS server or next proxy server, but not by other types of connection/transport/socket parameters, specifically in my case, negotiated SOCKS connections and outgoing connections which

Re: Is ink_freelist_new thread safe?

2011-05-25 Thread aniket ray
On Wed, May 25, 2011 at 8:12 PM, John Plevyak wrote: > There is no 64MB freelist unless you have created one yourself.  The buffer > freelists max out at 2MB and unless you are caching files you should not see > them allocated. > > john > I might have been mistaken but it seems ioBufAllocator[14]

Re: Is ink_freelist_new thread safe?

2011-05-25 Thread John Plevyak
Ah, yes, that is 64MB. The freelist is thread safe, although a missing "volatile" declaration caused it to fail to be so for the 32-bit version with recent versions of gcc. That is the reason to update to 2.1.8. Are you seeing your problem with a 32-bit or 64-bit build? john On Wed, May 25, 20