<feed xmlns='http://www.w3.org/2005/Atom'>
<title>otp.git/lib/tools, branch HansN-patch-1</title>
<subtitle>Mirror of Erlang/OTP repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/'/>
<entry>
<title>Merge branch 'rickard/signals/OTP-14589'</title>
<updated>2018-03-23T13:12:52+00:00</updated>
<author>
<name>Rickard Green</name>
<email>rickard@erlang.org</email>
</author>
<published>2018-03-23T13:12:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=5c2acbd35150da5e6d3afba1f61bb8bb995bb80f'/>
<id>5c2acbd35150da5e6d3afba1f61bb8bb995bb80f</id>
<content type='text'>
* rickard/signals/OTP-14589:
  Fix VM probes compilation
  Fix lock counting
  Fix signal order for is_process_alive
  Fix signal handling priority elevation
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* rickard/signals/OTP-14589:
  Fix VM probes compilation
  Fix lock counting
  Fix signal order for is_process_alive
  Fix signal handling priority elevation
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix signal order for is_process_alive</title>
<updated>2018-03-22T15:18:31+00:00</updated>
<author>
<name>Rickard Green</name>
<email>rickard@erlang.org</email>
</author>
<published>2018-03-21T15:33:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=f78ed9b50effd3007aafef2979ae5921ffedf75b'/>
<id>f78ed9b50effd3007aafef2979ae5921ffedf75b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #1740 from rickard-green/rickard/signals/OTP-14589</title>
<updated>2018-03-21T10:54:28+00:00</updated>
<author>
<name>Rickard Green</name>
<email>rickard@erlang.org</email>
</author>
<published>2018-03-21T10:54:28+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=cf3cbf0871832cb0808293842e5ae726edfc12e1'/>
<id>cf3cbf0871832cb0808293842e5ae726edfc12e1</id>
<content type='text'>
Implementation of true asynchronous signaling between processes</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Implementation of true asynchronous signaling between processes</pre>
</div>
</content>
</entry>
<entry>
<title>Implementation of true asynchronous signaling between processes</title>
<updated>2018-03-21T09:27:03+00:00</updated>
<author>
<name>Rickard Green</name>
<email>rickard@erlang.org</email>
</author>
<published>2018-03-07T00:17:21+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=4bc282d812cc2c49aa3e2d073e96c720f16aa270'/>
<id>4bc282d812cc2c49aa3e2d073e96c720f16aa270</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2018-03-14T08:58:15+00:00</updated>
<author>
<name>Henrik</name>
<email>henrik@erlang.org</email>
</author>
<published>2018-03-14T08:58:15+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=388b24ea7327ce8c7267b48c3a464ce8c404ddd6'/>
<id>388b24ea7327ce8c7267b48c3a464ce8c404ddd6</id>
<content type='text'>
Conflicts:
	OTP_VERSION
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Conflicts:
	OTP_VERSION
</pre>
</div>
</content>
</entry>
<entry>
<title>Update release notes</title>
<updated>2018-03-09T10:01:07+00:00</updated>
<author>
<name>Erlang/OTP</name>
<email>otp@erlang.org</email>
</author>
<published>2018-03-09T10:01:07+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=7c7ba7191a3932e737fa81fd0166df1c637d4b31'/>
<id>7c7ba7191a3932e737fa81fd0166df1c637d4b31</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Update version numbers</title>
<updated>2018-03-09T09:59:22+00:00</updated>
<author>
<name>Erlang/OTP</name>
<email>otp@erlang.org</email>
</author>
<published>2018-03-09T09:59:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=db5a9ef5e49f55338369f088bbef1d492f8c3c0c'/>
<id>db5a9ef5e49f55338369f088bbef1d492f8c3c0c</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2018-03-02T12:27:09+00:00</updated>
<author>
<name>Dan Gudmundsson</name>
<email>dgud@erlang.org</email>
</author>
<published>2018-03-02T12:27:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=bd5ebce131cc8a02e559b8eec2a68b089ca235a6'/>
<id>bd5ebce131cc8a02e559b8eec2a68b089ca235a6</id>
<content type='text'>
* maint:
  Add updated type-spec to Emacs skeletons of OTP behaviours
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* maint:
  Add updated type-spec to Emacs skeletons of OTP behaviours
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'pr/1620' into maint</title>
<updated>2018-03-02T12:26:21+00:00</updated>
<author>
<name>Dan Gudmundsson</name>
<email>dgud@erlang.org</email>
</author>
<published>2018-03-02T12:26:21+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=075baa1d95f225b60b9d9d53592cdfaecf81c24f'/>
<id>075baa1d95f225b60b9d9d53592cdfaecf81c24f</id>
<content type='text'>
* pr/1620:
  Add updated type-spec to Emacs skeletons of OTP behaviours
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* pr/1620:
  Add updated type-spec to Emacs skeletons of OTP behaviours
</pre>
</div>
</content>
</entry>
<entry>
<title>Add updated type-spec to Emacs skeletons of OTP behaviours</title>
<updated>2018-03-02T11:26:52+00:00</updated>
<author>
<name>Hamidreza Soleimani</name>
<email>hamidreza.s@gmail.com</email>
</author>
<published>2017-11-05T14:00:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/otp.git/commit/?id=41989853942f90763b21103958d8b2c0889f3728'/>
<id>41989853942f90763b21103958d8b2c0889f3728</id>
<content type='text'>
The changes are based on the latest versions of following modules
and are also similar to gen_statem Emacs skeleton. Note that the
gen_fsm is not updated because it is deprecated.

application:
* add/update type-spec for all callbacks
* add start_phase/3 callback
* add prep_stop/1 callback
* add config_change/3 callback

supervisor:
* add/update type-spec for all callbacks

supervisor_bridge:
* add/update type-spec for all callbacks

gen_server:
* add/update type-spec for all callbacks
* add format_status/2 callback

gen_event:
* add/update type-spec for all callbacks
* add format_status/2 callback
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The changes are based on the latest versions of following modules
and are also similar to gen_statem Emacs skeleton. Note that the
gen_fsm is not updated because it is deprecated.

application:
* add/update type-spec for all callbacks
* add start_phase/3 callback
* add prep_stop/1 callback
* add config_change/3 callback

supervisor:
* add/update type-spec for all callbacks

supervisor_bridge:
* add/update type-spec for all callbacks

gen_server:
* add/update type-spec for all callbacks
* add format_status/2 callback

gen_event:
* add/update type-spec for all callbacks
* add format_status/2 callback
</pre>
</div>
</content>
</entry>
</feed>
