Thanks. Applied! Cheers, Michael On 05/06/2014 08:53 AM, Peng Haitao wrote: > The function sched_getcpu() is thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/sched_getcpu.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/sched_getcpu.3 b/man3/sched_getcpu.3 > index 54b2483..7e2d395 100644 > --- a/man3/sched_getcpu.3 > +++ b/man3/sched_getcpu.3 > @@ -23,7 +23,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH SCHED_GETCPU 3 2014-04-28 "Linux" "Linux Programmer's Manual" > +.TH SCHED_GETCPU 3 2014-05-06 "Linux" "Linux Programmer's Manual" > .SH NAME > sched_getcpu \- determine CPU on which the calling thread is running > .SH SYNOPSIS > @@ -69,6 +69,11 @@ This kernel does not implement > .BR getcpu (2). > .SH VERSIONS > This function is available since glibc 2.6. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR sched_getcpu () > +function is thread-safe. > .SH CONFORMING TO > .BR sched_getcpu () > is glibc-specific. > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
