From 67ed5d1f21e939467a9441bab00aa8aacfa1be47 Mon Sep 17 00:00:00 2001 From: Murali Shankar Date: Wed, 27 Aug 2014 12:15:04 -0700 Subject: [PATCH] Added documentation for memlock_all to the release notes --- documentation/RELEASE_NOTES.html | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index 3db8233c0..d70bb4c39 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -15,6 +15,29 @@ EPICS Base 3.15.0.x releases are not intended for use in production systems.

Changes between 3.15.0.1 and 3.15.0.2

+

On POSIX systems, attempt to lock all memory on startup if running with a FIFO scheduler

+ +

+On POSIX systems, an IOC application's ability to meet timing deadlines is often +dependent on its ability to lock part or all of the process's virtual +address space into RAM, preventing that memory from being paged to the swap +area. This change will attempt to lock the process's virtual address space into +RAM if the process has the ability to run threads with different priorities. If +unsuccessful, it prints an message to stderr and continues. + +In Linux, one can grant a process the ability to run threads with different +priorities by using a command like ulimit -r unlimited. To use the FIFO +scheduler, use a command like so - chrt -f 1 softIoc -d test.db + +In Linux, one can grant a process the ability to lock memory by using a command +like ulimit -l unlimited. Alternatively, these limits can be configured on a per +user/per group basis by changing /etc/security/limits.conf or its equivalent. + +In Linux, a child process created via fork inherits its parent's resource +limits. Thus, it is probably a good idea to start the caRepeater before +starting the IOC. +

+

Implement EPICS_CAS_INTF_ADDR_LIST in rsrv

The IOC server can now bind to a single IP address (and optional port number)