#13880: Respect ulimit -v for GAP memory pool size
--------------------------------+-------------------------------------------
Reporter: vbraun | Owner: jason
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-5.6
Component: misc | Resolution:
Keywords: | Work issues: mem.available_swap() can be
negative
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by vbraun):
The problem is that I don't know an easy way to report "available swap".
It could all be reserved by some other gap session for all we know. So
`Total-Committed_AS` is a good approximation. Yes it can go negative if
the kernel is overcommitting, but one could argue that it is then to be
expected that a negative number is returned. In any case, it works as I
intended it. If you have a better metric for available swap that doesn't
involve going through the VM allocations of every process then I'd be
happy to implement that. But in its present state it is good enough for
starting GAP; if `Committed_AS > Total` then you probably want the
minimial sized pool for GAP.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13880#comment:24>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
