Commit 06785a48 by Daniel Franke Committed by Daniel Franke

libgomp.texi (GOMP_CPU_AFFINITY): Updated.

2007-04-19  Daniel Franke  <franke.daniel@gmail.com>

        * libgomp.texi (GOMP_CPU_AFFINITY): Updated.

From-SVN: r123976
parent 93167356
2007-04-19 Daniel Franke <franke.daniel@gmail.com>
* libgomp.texi (GOMP_CPU_AFFINITY): Updated.
2007-04-16 Matthias Klose <doko@debian.org> 2007-04-16 Matthias Klose <doko@debian.org>
* configure.tgt (i[456]86-*-linux*): Only add ia32 specific * configure.tgt (i[456]86-*-linux*): Only add ia32 specific
......
...@@ -895,14 +895,25 @@ dynamic scheduling and a chunk size of 1 is used. ...@@ -895,14 +895,25 @@ dynamic scheduling and a chunk size of 1 is used.
@cindex Environment Variable @cindex Environment Variable
@table @asis @table @asis
@item @emph{Description}: @item @emph{Description}:
A patch for this extension has been submitted, but was not yet applied at the Binds threads to specific CPUs. The variable should contain a space- or
time of writing. comma-separated list of CPUs. This list may contain different kind of
entries: either single CPU numbers in any order, a range of CPUs (M-N)
@item @emph{Reference}: or a range with some stride (M-N:S). CPU numbers are zero based. For example,
@uref{http://gcc.gnu.org/ml/gcc-patches/2006-05/msg00982.html, @code{GOMP_CPU_AFFINITY="0 3 1-2 4-15:2"} will bind the initial thread
GCC Patches Mailinglist} to CPU 0, the second to CPU 3, the third to CPU 1, the fourth to
@uref{http://gcc.gnu.org/ml/gcc-patches/2006-05/msg01133.html, CPU 2, the fifth to CPU 4, the sixth through tenth to CPUs 6, 8, 10, 12,
GCC Patches Mailinglist} and 14 respectively and then start assigning back from the beginning of
the list. @code{GOMP_CPU_AFFINITY=0} binds all threads to CPU 0.
There is no GNU OpenMP library routine to determine whether a CPU affinity
specification is in effect. As a workaround, language-specific library
functions, e.g., @code{getenv} in C or @code{GET_ENVIRONMENT_VARIABLE} in
Fortran, may be used to query the setting of the @code{GOMP_CPU_AFFINITY}
environment variable. A defined CPU affinity on startup cannot be changed
or disabled during the runtime of the application.
If this environment variable is omitted, the host system will handle the
assignment of threads to CPUs.
@end table @end table
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment