For SWAP there is a new kstat:
caps:{zoneid}:swapresv_zone_{zoneid}
The only way I know how to calculate how much memory a zone is using is
via /proc and filter on the zoneid
Michel Schuster wrote:
> Dear Steven,
>
> Do you have any updates regarding zone observability features. I've
> downlo
Dear Steven,
Do you have any updates regarding zone observability features. I've downloaded
Solaris10 U4 and need to monitor the used memory per zone, plus swap and locked
memory used.
Ideally, DTrace scripts would be welcome.
Do you have any clues on this subject ?
Right now, I'm only able to
Allan Packer wrote:
Hi,
Does this code modify rcapd to properly account for shared memory?
That particular feature was mentioned in the case materials for PSARC
2006/496, but I wasn't clear on whether it made it in or not.
Allan,
Yes, we added new support in the kernel to account for this
Hi,
Does this code modify rcapd to properly account for shared memory?
That particular feature was mentioned in the case materials for PSARC
2006/496, but I wasn't clear on whether it made it in or not.
TIA,
Allan
On 06/02/2007, at 4:42 PM, Jerry Jelinek wrote:
Mike,
Mike Gerdts wro
On Mon, Feb 05, 2007 at 10:17:42PM -0600, Mike Gerdts wrote:
> I just got a chance to start playing with the capped memory resource
> controls in build 56. At first blush, this looks to be *very* good
> stuff. My initial testing included some very basic single process
> memory hog tests and multi
Mike,
Mike Gerdts wrote:
One of the effects of setting capped-memory resource control for swap
is that the size of /tmp is also limited. Unlike when a tmpfs size
limit is set with the size=... mount option, "df /tmp" does not
display a value that is reflective of the limits that are put in
plac
On Mon 05 Feb 2007 at 10:17PM, Mike Gerdts wrote:
> I just got a chance to start playing with the capped memory resource
> controls in build 56. At first blush, this looks to be *very* good
> stuff. My initial testing included some very basic single process
> memory hog tests and multiple process
I just got a chance to start playing with the capped memory resource
controls in build 56. At first blush, this looks to be *very* good
stuff. My initial testing included some very basic single process
memory hog tests and multiple process mmap(..., MAP_SHARED,...) tests.
In each case, the limit