Re: where is the memory being held

2010-10-01 Thread zhu qun-ying
Message > From: David Schwartz > To: openssl-users@openssl.org > Cc: Scott Neugroschl > Sent: Tue, September 28, 2010 3:08:48 PM > Subject: Re: where is the memory being held > > On 9/27/2010 4:13 PM, Scott Neugroschl wrote: > > As David said, yes. > >

Re: where is the memory being held

2010-09-28 Thread David Schwartz
On 9/27/2010 4:13 PM, Scott Neugroschl wrote: As David said, yes. On the other hand, you could re-implement malloc() and free() for your platform. There's really no way to make that help very much. It might help a little, but the fundamental problem is this: If you want to implement each 'ma

RE: where is the memory being held

2010-09-27 Thread Scott Neugroschl
As David said, yes. On the other hand, you could re-implement malloc() and free() for your platform. From: owner-openssl-us...@openssl.org on behalf of zhu qun-ying Sent: Sun 9/26/2010 11:14 PM To: openssl-users@openssl.org Subject: Re: where is the memory

Re: where is the memory being held

2010-09-27 Thread David Schwartz
On 9/26/2010 11:14 PM, zhu qun-ying wrote: Does it mean that it is hard to change the behavior? Yes, because it's not implemented in any one particular place. It's a fundamental design assumption throughout OpenSSL that it's aimed at general-purpose computers with virtual memory subsystems.

Re: where is the memory being held

2010-09-26 Thread zhu qun-ying
Does it mean that it is hard to change the behavior? -- qun-ying --- On Fri, 9/24/10, David Schwartz wrote: > > Sounds like OpenSSL wasn't what you wanted. OpenSSL is > intended for use on general-purpose computers with virtual > memory. It is not designed to return virtual memory to the > syst

Re: where is the memory being held

2010-09-24 Thread David Schwartz
On 9/24/2010 11:05 AM, zhu qun-ying wrote: I think I should clarify something here. The app is running > in a small device that does not have virtual memory (no swap space) and the memory is limited (256/512 M). > In peek connections, it may use up to 90% of the system memory, > and when con

Re: where is the memory being held

2010-09-24 Thread Michael S. Zick
On Fri September 24 2010, zhu qun-ying wrote: > Hi, > > I think I should clarify something here. The app is running in a small > device that does not have virtual memory (no swap space) and the memory is > limited (256/512 M). In peek connections, it may use up to 90% of the system > memory,

Re: where is the memory being held

2010-09-24 Thread zhu qun-ying
Hi, I think I should clarify something here. The app is running in a small device that does not have virtual memory (no swap space) and the memory is limited (256/512 M). In peek connections, it may use up to 90% of the system memory, and when connection goes down, memory usage is not coming

Re: where is the memory being held

2010-09-23 Thread David Schwartz
On 9/23/2010 11:42 AM, zhu qun-ying wrote: Hi, I have an SSL apllication, that it suppose to run for a long time. After some time of running, I found the usage of the memory is growing. I stop all SSL connections and checked all SSL * has been freed but it could not release the memory back

where is the memory being held

2010-09-23 Thread zhu qun-ying
Hi, I have an SSL apllication, that it suppose to run for a long time. After some time of running, I found the usage of the memory is growing. I stop all SSL connections and checked all SSL * has been freed but it could not release the memory back to the system. After some investigation, I f