Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2025-12-16 01:34:58 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

sched/signal: In signal notification facility, use sigqueue() to notify vs. kill(). With sigqueue, we can pass more info (but still not enough).

Browse Source
This commit is contained in:
Gregory Nutt
2018-09-09 11:57:25 -06:00
parent 32e3e51678
commit 20814acad2
7 changed files with 212 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
net/tcp/tcp.h
View File

@@ -1552,6 +1552,10 @@ int tcp_pollteardown(FAR struct socket *psock, FAR struct pollfd *fds);
* to block signal delivery. The signal will be delivered once the
* signal is removed from the sigprocmask.
*
* NOTE: If sigwaitinfo() or sigtimedwait() are used to catch the signal
* then then TCP connection structure pointer may be recovered in the
* sival_ptr value of the struct siginfo instance.
*
* Input Parameters:
* pid - The PID to be notified. If a zero value is provided, then the
* PID of the calling thread will be used.
@@ -1609,6 +1613,10 @@ int tcp_notifier_teardown(int key);
* the highest priority thread will get the data. Lower priority threads
* will need to call tcp_notifier_setup() once again.
*
* NOTE: If sigwaitinfo() or sigtimedwait() are used to catch the signal
* then then TCP connection structure pointer may be obtained in the
* sival_ptr value of the struct siginfo instance.
*
* Input Parameters:
* conn - The TCP connection where read-ahead data was just buffered.
*

8
net/tcp/tcp_notifier.c
View File

@@ -62,6 +62,10 @@
* to block signal delivery. The signal will be delivered once the
* signal is removed from the sigprocmask.
*
* NOTE: If sigwaitinfo() or sigtimedwait() are used to catch the signal
* then then TCP connection structure pointer may be recovered in the
* sival_ptr value of the struct siginfo instance.
*
* Input Parameters:
* pid - The PID to be notified. If a zero value is provided, then the
* PID of the calling thread will be used.
@@ -134,6 +138,10 @@ int tcp_notifier_teardown(int key)
* the highest priority thread will get the data. Lower priority threads
* will need to call tcp_notifier_setup() once again.
*
* NOTE: If sigwaitinfo() or sigtimedwait() are used to catch the signal
* then then TCP connection structure pointer may be obtained in the
* sival_ptr value of the struct siginfo instance.
*
* Input Parameters:
* conn - The TCP connection where read-ahead data was just buffered.
*