Shashidar Umavenkata-G19816 wrote:
>  Hans,
> 
> I have query on memory wastage, As  my understanding thread stack size
> will occupy more  virtual space of a process but not the RAM then how
> memory is going to be wasted.

That might be correct unless a process have used the mlock system call.

Looking closely at a certain opensaf process using e.g. 'cat /proc/1433/smaps' 
one sees all the 8MB stacks allocated in the process.

b547a000-b5c7a000 rw-p b547a000 00:00 0
Size:              8192 kB
Rss:                 12 kB
Shared_Clean:         0 kB
Shared_Dirty:         0 kB
Private_Clean:        0 kB
Private_Dirty:       12 kB

The Rss column indicates how much physical resident memory is currently mapped 
into this region. Rss in fact would be a good indicator to set the stack size 
in 
each thread. Just run some tests and check Rss for all threads. Then set stack 
size to lets say Rss*2 for each thread.

So physical memory is perhaps not allocated unless a process use the mlock() 
call. Which all real time processes should meaning perhaps its missing in 
OpenSAF?

Anyway quickly looking at an OpenSAF system using 'top' or 'free' indicates 
that 
  ~600MB is used by the base system only. Therefore my concern about the "look 
and feel" of the system.

This is my interpretation, I hope it is correct.

Regards,
Hans

 > However I agree large virtual space could
> lead to big core dumps which might get truncated.
> 
> Regards,
> Shashi.
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Hans Feldt
> Sent: Thursday, November 15, 2007 3:29 PM
> To: Betham R-G19443
> Cc: [email protected]
> Subject: Re: [Users] Opensaf1.0-4 Release
> 
> Not solved (thread stack size):
> 
> http://list.opensaf.org/archives/users/2007-August/000179.html
> 
> I think this one is really important. Core dumps gets too big and
> truncated, memory is wasted & the system looks less attractive to
> applications (no memory left).
> 
> I spent a lot of time and effort creating this patch, why is it not
> included?
> 
> Why bring in new features without fixing issues in the existing ones?
> 
> Regards,
> Hans
> 
> 
> Betham R-G19443 wrote:
>> Yes, it is correct.
>>
>> Thanks,
>> Ramesh.
>>
>>> -----Original Message-----
>>> From: [EMAIL PROTECTED] 
>>> [mailto:[EMAIL PROTECTED] On Behalf Of Hans Feldt
>>> Sent: Wednesday, November 14, 2007 5:47 PM
>>> To: Murthy E-G19462
>>> Cc: [email protected]
>>> Subject: Re: [Users] Opensaf1.0-4 Release
>>>
>>> Thanks! Just need some clarification what's in and what's not.
>>>
>>> Not solved:
>>> http://list.opensaf.org/archives/users/2007-August/000252.html
>>>
>>> Solved:
>>> http://list.opensaf.org/archives/users/2007-September/000392.html
>>>
>>> Is that correct?
>>>
>>> Regards,
>>> Hans
>>>
>>> Murthy E-G19462 wrote:
>>>> All,
>>>>
>>>> You can download the opensaf1.0-4 release from below link.
>>>> http://www.opensaf.org/download
>>>>
>>>> Key features of the drop.
>>>>
>>>> - HPI B spec support
>>>> - Tested openSAF1.0-4 release on Debian4.0R1 (going forward Debian 
>>>> major releases are going to be
>>>>   the reference platform for testing opensaf).
>>>> - Cleanup of unwanted shared libraries, SPSv code and inclusion of 
>>>>   public header files in the rpm.
>>>> - UML patch to use net-snmp source code.
>>>>
>>>> Detailed description of the features are available in Changelog.
>>>> Also read the updated INSTALL file.
>>>>
>>>> Note: Dynamic loading of the SAF agent libraries is not included in 
>>>> this drop.
>>>> We experienced some timing issues and inconsistent behavior while 
>>>> loading these Libraries. So these changes are taken out of the 
>>>> release.
>>>>
>>>> Regards
>>>> Murthy
>>>> _______________________________________________
>>>> Users mailing list
>>>> [email protected]
>>>> http://list.opensaf.org/maillist/listinfo/users
>>>>
>>> _______________________________________________
>>> Users mailing list
>>> [email protected]
>>> http://list.opensaf.org/maillist/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> [email protected]
>> http://list.opensaf.org/maillist/listinfo/users
>>
> 
> _______________________________________________
> Users mailing list
> [email protected]
> http://list.opensaf.org/maillist/listinfo/users
> 

_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users

Reply via email to