aboutsummaryrefslogtreecommitdiffstats
path: root/bootstrap/lib/kernel/ebin/kernel.appup
AgeCommit message (Collapse)Author
2018-04-27Update primary bootstrapBjörn Gustavsson
2018-04-26Remove error_logger process and add logger processSiri Hansen
2018-03-21Implementation of true asynchronous signaling between processesRickard Green
Communication between Erlang processes has conceptually always been performed through asynchronous signaling. The runtime system implementation has however previously preformed most operation synchronously. In a system with only one true thread of execution, this is not problematic (often the opposite). In a system with multiple threads of execution (as current runtime system implementation with SMP support) it becomes problematic. This since it often involves locking of structures when updating them which in turn cause resource contention. Utilizing true asynchronous communication often avoids these resource contention issues. The case that triggered this change was contention on the link lock due to frequent updates of the monitor trees during communication with a frequently used server. The signal order delivery guarantees of the language makes it hard to change the implementation of only some signals to use true asynchronous signaling. Therefore the implementations of (almost) all signals have been changed. Currently the following signals have been implemented as true asynchronous signals: - Message signals - Exit signals - Monitor signals - Demonitor signals - Monitor triggered signals (DOWN, CHANGE, etc) - Link signals - Unlink signals - Group leader signals All of the above already defined as asynchronous signals in the language. The implementation of messages signals was quite asynchronous to begin with, but had quite strict delivery constraints due to the ordering guarantees of signals between a pair of processes. The previously used message queue partitioned into two halves has been replaced by a more general signal queue partitioned into three parts that service all kinds of signals. More details regarding the signal queue can be found in comments in the erl_proc_sig_queue.h file. The monitor and link implementations have also been completely replaced in order to fit the new asynchronous signaling implementation as good as possible. More details regarding the new monitor and link implementations can be found in the erl_monitor_link.h file.
2017-10-13Update primary bootstrapBjörn Gustavsson
2017-08-16Update primary bootstrapBjörn Gustavsson
2017-07-07Update primary bootstrapBjörn Gustavsson
2017-06-14Update primary bootstrapRickard Green
2017-02-17Update primary bootstrapBjörn Gustavsson
2016-11-23Update primary bootstrapBjörn Gustavsson
2016-09-29Update primary bootstrapBjörn Gustavsson
2016-08-10Update primary bootstrapBjörn Gustavsson
2016-04-18Update primary bootstrapBjörn Gustavsson
2016-03-21Update primary bootstrapBjörn Gustavsson
2015-12-17Update primary bootstrapBjörn Gustavsson
2015-09-21Update primary bootstrapBjörn Gustavsson
2015-06-18Change license text to APLv2Bruce Yinhe
2015-06-04Update primary bootstrapBjörn Gustavsson
2015-05-08Update primary bootstrapBjörn Gustavsson
2015-01-21Merge branch 'maint'Björn Gustavsson
* maint: Update primary bootstrap core_lib: Handle patterns in map values
2015-01-21Update primary bootstrapBjörn Gustavsson
2014-12-09Update primary bootstrapMarcus Arendt
2014-10-03Update primary bootstrapBjörn-Egil Dahlberg
2014-09-01Update primary bootstrapBjörn Gustavsson
2014-02-26Update preloaded and primary bootstrapRickard Green
2014-01-28Update primary bootstrapBjörn-Egil Dahlberg
2013-05-06Update primary bootstrapHans Bolinder
2013-02-04Update primary bootstrapBjörn Gustavsson
2012-06-25Merge branch 'maint'Björn Gustavsson
* maint: Update primary bootstrap sys_pre_expand: Eliminate bottleneck for modules with many functions Conflicts: bootstrap/bin/start.boot bootstrap/bin/start_clean.boot bootstrap/lib/kernel/ebin/file.beam bootstrap/lib/kernel/ebin/hipe_unified_loader.beam
2011-09-14primary bootstrap: Remove source filesBjörn Gustavsson
The primary bootstrap contains generated source files that are not needed for building Erlang/OTP. Since these files contains dates, version numbers, or absolute path names, new versions of most of those files will be created in the git repository every time the primary bootstrap is updated, thus growing the git repository grow more than necessary.
2011-03-11Update primary bootstrapBjörn-Egil Dahlberg
2010-12-03Update primary bootstrapPatrik Nyblom
2010-04-01Update bootstrap compilerBjörn Gustavsson
2009-12-11Update bootstrap compilerBjörn Gustavsson
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP