Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Dom0 memory allocation?



On 12 Mar 2015, at 19:35 , tg%gmplib.org@localhost wrote:
[…]
> The big hog is xentop.
> 
> Oh, wait a minute.  When I now restarted xentop, it disappeared from the
> list.  But the xentop from above had not run more than a few hours.
> When the system died, I think a xentop had run for two or three days.
> 
> Running
>  while true; do ps agux | grep xento[p]; sleep 60; done
> for a few minutes reveals tell-tale data:
> 
> root    3096  0.0  0.3  28044  6452 pts/4  S+    6:32PM 0:00.15 xentop 
> root    3096  0.0  0.3  29068  7320 pts/4  S+    6:32PM 0:00.18 xentop 
> root    3096  0.0  0.4  30092  8184 pts/4  S+    6:32PM 0:00.21 xentop 
> root    3096  0.0  0.4  31116  9048 pts/4  S+    6:32PM 0:00.24 xentop 
> root    3096  0.0  0.5  31116  9904 pts/4  S+    6:32PM 0:00.27 xentop 
> root    3096  0.0  0.5  32140 10776 pts/4  S+    6:32PM 0:00.30 xentop 
> root    3096  0.0  0.6  33164 11640 pts/4  S+    6:32PM 0:00.33 xentop 
> root    3096  0.0  0.6  34188 12512 pts/4  S+    6:32PM 0:00.36 xentop 
> root    3096  0.0  0.6  35212 13376 pts/4  S+    6:32PM 0:00.39 xentop 
> root    3096  0.0  0.7  36236 14248 pts/4  S+    6:32PM 0:00.42 xentop 
> 
> I think I'm starting to understand why 1 GiB Dom0 allocation was not
> enough.  :-)
> 
> It is possible to speed up the leak by passing -d 0.5 to xentop.
> 
> (I tried to wrap xentop in a bash script which runs ulimit with -d -s -m
> with ridiculously low argument values.  It seem most if these are
> actually not setting sysrlimit properly; only -v successfully forced
> xentop to die.)

Did you send-pr(1) on this?

(A quick query on http://www.netbsd.org/support/query-pr.html didn't
give a hit…)

/P


Home | Main Index | Thread Index | Old Index