Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Aug 2010 15:10:57 GMT
From:      Edward Tomasz Napierala <trasz@FreeBSD.org>
To:        Perforce Change Reviews <perforce@freebsd.org>
Subject:   PERFORCE change 182029 for review
Message-ID:  <201008071510.o77FAvOl006387@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@182029?ac=10

Change 182029 by trasz@trasz_victim on 2010/08/07 15:10:09

	Update TODO.

Affected files ...

.. //depot/projects/soc2009/trasz_limits/TODO#23 edit

Differences ...

==== //depot/projects/soc2009/trasz_limits/TODO#23 (text+ko) ====

@@ -7,13 +7,13 @@
  - virtual memory usage (address space limit) (RUSAGE_VMEM), in megabytes
  - maximum core size (RUSAGE_CORE), in megabytes (core, as in ELF program state dump)
  - locked memory usage (RUSAGE_MEMLOCK), in megabytes
+ - resident set size (physical memory usage) (RUSAGE_RSS), in megabytes
 
 Limits to do:
 
 Milestone 1:
 
  - stack size (RUSAGE_STACK), in megabytes,
- - resident set size (physical memory usage) (RUSAGE_RSS), in megabytes
  - swap usage (RUSAGE_SWAP), in megabytes
  - number of file descriptors (RUSAGE_NOFILE)
  - amount of memory consumed by socket buffers (RUSAGE_SBSIZE), in megabytes
@@ -62,6 +62,8 @@
    container mechanism.  This is a part of HRL, and it's outside the scope
    of the containers project.  This means the code is full of "#ifdef CONTAINERS".
 
+ - RSS is accounted for only when pagedaemon is running, i.e. when memory shortage occurs.
+
  - Don't account resources for system processes.  It's not as easy as checking
    for P_SYSTEM flag, as the flag will be set for AIO kernel processes.
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008071510.o77FAvOl006387>