AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2025-01-05 09:01:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Stylistic changes to make HTML generation easier.

Browse Source
This commit is contained in:
Andreas Jaeger 2001-05-05 14:43:14 +00:00
parent aa2e3ec386
commit bcd249f638
1 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ.in
View File

@ -1602,24 +1602,24 @@ this should be necessary.
supports synchronous context switches only. There are several reasons for supports synchronous context switches only. There are several reasons for
this: this:
o UNIX provides no other (portable) way of effecting a synchronous - UNIX provides no other (portable) way of effecting a synchronous
context switch (also known as co-routine switch). Some versions context switch (also known as co-routine switch). Some versions
support this via setjmp()/longjmp() but this does not work support this via setjmp()/longjmp() but this does not work
universally. universally.
o As defined by the UNIX '98 standard, the only way setcontext() - As defined by the UNIX '98 standard, the only way setcontext()
could trigger an asychronous context switch is if this function could trigger an asychronous context switch is if this function
were invoked on the ucontext_t pointer passed as the third argument were invoked on the ucontext_t pointer passed as the third argument
to a signal handler. But according to draft 5, XPG6, XBD 2.4.3, to a signal handler. But according to draft 5, XPG6, XBD 2.4.3,
setcontext() is not among the set of routines that may be called setcontext() is not among the set of routines that may be called
from a signal handler. from a signal handler.
o If setcontext() were to be used for asynchronous context switches, - If setcontext() were to be used for asynchronous context switches,
all kinds of synchronization and re-entrancy issues could arise and all kinds of synchronization and re-entrancy issues could arise and
these problems have already been solved by real multi-threading these problems have already been solved by real multi-threading
libraries (e.g., POSIX threads or Linux threads). libraries (e.g., POSIX threads or Linux threads).
o Synchronous context switching can be implemented entirely in - Synchronous context switching can be implemented entirely in
user-level and less state needs to be saved/restored than for an user-level and less state needs to be saved/restored than for an
asynchronous context switch. It is therefore useful to distinguish asynchronous context switch. It is therefore useful to distinguish
between the two types of context switches. Indeed, some between the two types of context switches. Indeed, some