|
From: | Markus Mützel |
Subject: | [Octave-patch-tracker] [patch #9924] Suggestion for a memory() function |
Date: | Thu, 21 May 2020 14:43:37 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0 |
Update of patch #9924 (project octave): Status: None => In Progress _______________________________________________________ Follow-up Comment #22: I went ahead and removed the linux tag, adapted the code to the coding standards, added calling the __wmemory__ function on Windows and created a patch with Lars as the author. It applies on top of the wmemory patch. I also added a fallback to MemFree if MemAvailable doesn't exist in proc/meminfo. Is this ok? Or is there something better we can do? We should probably flesh out the documentation a little bit more, i.e. explain the meaning of the fields in the returned structures. Querying the actual size of the user address space on Linux as well as support on Mac would be nice. But that could also be added at a later point imho. (file #49140) _______________________________________________________ Additional Item Attachment: File name: patch9924_memory.patch Size:9 KB <https://savannah.gnu.org/file/patch9924_memory.patch?file_id=49140> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/patch/?9924> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |