From 1a8620f03ea3224e0040caee8863842f3d1df095 Mon Sep 17 00:00:00 2001
From: Ralph Lange
EPICS Base 3.15.0.x releases are not intended for use in production systems.EPICS Base Release 3.15.0.1
+EPICS Base Release 3.15.0.2
The general purpose callback facility can run multiple parallel callback +threads per priority level. This makes better use of SMP architectures (e.g. +processors with multiple cores), as callback work - which includes second +stage processing of records with asynchronuous device support and I/O +scanned processing - can be distributed over the available CPUs.
+ +Note that by using parallel callback threads the order of scan callback +requests in the queue is not retained. If a device support needs to be +informed when scanIoRequest processing has finished, it should use the new +scanIoSetComplete() feature to add a user function that will be called after +the scanIoRequest record processing has finished.
+ +Parallel callback threads have to be explicitly configured, by default +the IOC keeps the old behavior of running one callback thread per priority.
+The IOC server can now bind to a single IP address (and optional port number) @@ -31,8 +48,7 @@ backwards compatibility reasons. Only the alarm.h header needs to be included now to declare the epicsAlarmSeverityStrings and epicsAlarmConditionStrings arrays.
-A general purpose threaded work queue API epicsThreadPool is added.