Re: [zones-discuss] Capped-Memory - swap physical? (was: Failing to NFS mount on non-global zone)
Hi, So if we want a to configure a Zone with 4 GB physical memory and max 2 GB swap the values have to be capped-memory: physical: 4G [swap: 6G] Is that correct? I just reread the documentation about swap and from that it's not clear to me that swap in the zone configuration is used that way regards Bernd -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Capped-Memory - swap physical? (was: Failing to NFS mount on non-global zone)
Your config is basically what you want. The zone will be able to reserve up to 6gb of memory, 4 of which may reside in physical memory. The 4gb of ram is not reserved for the zone, so the zone could get less RAM due to global memory pressure, and use more than 2gb of disk swap. For instance, the zone could get 3 gb of ram and 3gb of disk swap (for a total of 6gb of virtual memory). -Steve L. On Mon, Feb 23, 2009 at 09:06:13PM +0100, Bernd Schemmer wrote: Hi, So if we want a to configure a Zone with 4 GB physical memory and max 2 GB swap the values have to be apped-memory: physical: 4G [swap: 6G] Is that correct? I just reread the documentation about swap and from that it's not clear to me that swap in the zone configuration is used that way regards Bernd Steve Lawrence wrote: Swap limits how much of the systems total memory (ram + disk) can be reserved. When this limit is hit, allocations, such as malloc, will fail. Physical memory limits resident memory. When this limit is hit, the zone will page pages in memory to disk swap. In general, your example config is only useful if the zone uses a lot of physical memory, but does not reserve as much swap. An example is an application which maps a large on-disk file into memory. No swap is needed for the file, (because the file can be paged back to the a filesystem), but a large amount of physical memory may be needed to pull the file into RAM. Such applications are rare, so your example config is not often used. Your basically right is saying that this config does not make any sense in most cases. -Steve L. On Fri, Feb 20, 2009 at 08:36:20PM +0100, Alexander Skwar wrote: Hi! On Fri, Feb 20, 2009 at 17:50, Asif Iqbal vad...@gmail.com wrote: capped-memory: physical: 1G [swap: 512M] A question regarding this setting - does that setting really make sense? I suppose he tries to achieve that the zone as a max. uses 1G of real memory and no more than 512M of Swap. But does it really do that? Or is he rather limiting the amount of allocable mem to 512M? Alexander -- [ Soc. = http://twitter.com/alexs77 | http://www.plurk.com/alexs77 ] [ Mehr = http://zyb.com/alexws77 ] [ Chat = Jabber: alexw...@jabber80.com | Google Talk: a.sk...@gmail.com ] [ Mehr = MSN: alexw...@live.de | Yahoo!: askwar | ICQ: 350677419 ] ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org -- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Capped-Memory - swap physical? (was: Failing to NFS mount on non-global zone)
Hi! On Fri, Feb 20, 2009 at 17:50, Asif Iqbal vad...@gmail.com wrote: capped-memory: physical: 1G [swap: 512M] A question regarding this setting - does that setting really make sense? I suppose he tries to achieve that the zone as a max. uses 1G of real memory and no more than 512M of Swap. But does it really do that? Or is he rather limiting the amount of allocable mem to 512M? Alexander -- [ Soc. = http://twitter.com/alexs77 | http://www.plurk.com/alexs77 ] [ Mehr = http://zyb.com/alexws77 ] [ Chat = Jabber: alexw...@jabber80.com | Google Talk: a.sk...@gmail.com ] [ Mehr = MSN: alexw...@live.de | Yahoo!: askwar | ICQ: 350677419 ] ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Capped-Memory - swap physical? (was: Failing to NFS mount on non-global zone)
Swap limits how much of the systems total memory (ram + disk) can be reserved. When this limit is hit, allocations, such as malloc, will fail. Physical memory limits resident memory. When this limit is hit, the zone will page pages in memory to disk swap. In general, your example config is only useful if the zone uses a lot of physical memory, but does not reserve as much swap. An example is an application which maps a large on-disk file into memory. No swap is needed for the file, (because the file can be paged back to the a filesystem), but a large amount of physical memory may be needed to pull the file into RAM. Such applications are rare, so your example config is not often used. Your basically right is saying that this config does not make any sense in most cases. -Steve L. On Fri, Feb 20, 2009 at 08:36:20PM +0100, Alexander Skwar wrote: Hi! On Fri, Feb 20, 2009 at 17:50, Asif Iqbal vad...@gmail.com wrote: capped-memory: physical: 1G [swap: 512M] A question regarding this setting - does that setting really make sense? I suppose he tries to achieve that the zone as a max. uses 1G of real memory and no more than 512M of Swap. But does it really do that? Or is he rather limiting the amount of allocable mem to 512M? Alexander -- [ Soc. = http://twitter.com/alexs77 | http://www.plurk.com/alexs77 ] [ Mehr = http://zyb.com/alexws77 ] [ Chat = Jabber: alexw...@jabber80.com | Google Talk: a.sk...@gmail.com ] [ Mehr = MSN: alexw...@live.de | Yahoo!: askwar | ICQ: 350677419 ] ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Capped-Memory - swap physical? (was: Failing to NFS mount on non-global zone)
We run into this problem repeatedly... swap in Solaris terms refers to total VM. This is true on most UNIX systems. However, we often mistakenly refer to pagefile (swap disk) simply and incorrectly as swap. Therefore, the swap cap is better thought of as a VM cap. Rcapd (physical) will keep RSS in check. When exceeded it will page out to the page file (swap disk). When total VM (RSS+Pagefile+tmpfs) exceeds the zone.max-swap limit malloc() will fail. Thus, swap is the right term, but its almost universally misused. Best example is the swap column in vmstat output. benr. Steve Lawrence wrote: Swap limits how much of the systems total memory (ram + disk) can be reserved. When this limit is hit, allocations, such as malloc, will fail. Physical memory limits resident memory. When this limit is hit, the zone will page pages in memory to disk swap. In general, your example config is only useful if the zone uses a lot of physical memory, but does not reserve as much swap. An example is an application which maps a large on-disk file into memory. No swap is needed for the file, (because the file can be paged back to the a filesystem), but a large amount of physical memory may be needed to pull the file into RAM. Such applications are rare, so your example config is not often used. Your basically right is saying that this config does not make any sense in most cases. -Steve L. On Fri, Feb 20, 2009 at 08:36:20PM +0100, Alexander Skwar wrote: Hi! On Fri, Feb 20, 2009 at 17:50, Asif Iqbal vad...@gmail.com wrote: capped-memory: physical: 1G [swap: 512M] A question regarding this setting - does that setting really make sense? I suppose he tries to achieve that the zone as a max. uses 1G of real memory and no more than 512M of Swap. But does it really do that? Or is he rather limiting the amount of allocable mem to 512M? Alexander -- [ Soc. = http://twitter.com/alexs77 | http://www.plurk.com/alexs77 ] [ Mehr = http://zyb.com/alexws77 ] [ Chat = Jabber: alexw...@jabber80.com | Google Talk: a.sk...@gmail.com ] [ Mehr = MSN: alexw...@live.de | Yahoo!: askwar | ICQ: 350677419 ] ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
