Movatterモバイル変換


[0]ホーム

URL:


Skip Navigation Links
Exit Print View
Link to oracle.comman pages section 2: System Calls    Oracle Solaris 11 Information Library
Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon
 Search Scope:

Document Information

Preface

Introduction

System Calls

access(2)

acct(2)

acl(2)

adjtime(2)

alarm(2)

brk(2)

chdir(2)

chmod(2)

chown(2)

chroot(2)

close(2)

creat(2)

dup(2)

exec(2)

execl(2)

execle(2)

execlp(2)

execv(2)

execve(2)

execvex(2)

execvp(2)

_Exit(2)

_exit(2)

exit(2)

faccessat(2)

facl(2)

fchdir(2)

fchmod(2)

fchmodat(2)

fchown(2)

fchownat(2)

fchroot(2)

fcntl(2)

fexecve(2)

fgetlabel(2)

fork1(2)

fork(2)

forkall(2)

forkallx(2)

forkx(2)

fpathconf(2)

fstat(2)

fstatat(2)

fstatvfs(2)

futimens(2)

futimesat(2)

getacct(2)

getcontext(2)

getdents(2)

getegid(2)

geteuid(2)

getgid(2)

getgroups(2)

getisax(2)

getitimer(2)

getlabel(2)

getmsg(2)

getpflags(2)

getpgid(2)

getpgrp(2)

getpid(2)

getpmsg(2)

getppid(2)

getppriv(2)

getprojid(2)

getrctl(2)

getrlimit(2)

getsid(2)

gettaskid(2)

getuid(2)

getustack(2)

ioctl(2)

issetugid(2)

kill(2)

lchown(2)

link(2)

linkat(2)

llseek(2)

lseek(2)

lstat(2)

_lwp_cond_broadcast(2)

_lwp_cond_reltimedwait(2)

_lwp_cond_signal(2)

_lwp_cond_timedwait(2)

_lwp_cond_wait(2)

_lwp_continue(2)

_lwp_info(2)

_lwp_kill(2)

_lwp_mutex_lock(2)

_lwp_mutex_trylock(2)

_lwp_mutex_unlock(2)

_lwp_self(2)

_lwp_sema_init(2)

_lwp_sema_post(2)

_lwp_sema_trywait(2)

_lwp_sema_wait(2)

_lwp_suspend(2)

memcntl(2)

meminfo(2)

mincore(2)

mkdir(2)

mkdirat(2)

mknod(2)

mknodat(2)

mmap(2)

mmapobj(2)

mount(2)

mprotect(2)

msgctl(2)

msgget(2)

msgids(2)

msgrcv(2)

msgsnap(2)

msgsnd(2)

munmap(2)

nice(2)

ntp_adjtime(2)

ntp_gettime(2)

open(2)

openat(2)

pathconf(2)

pause(2)

pcsample(2)

pipe(2)

poll(2)

p_online(2)

ppoll(2)

pread(2)

priocntl(2)

priocntlset(2)

processor_bind(2)

processor_info(2)

profil(2)

pset_assign(2)

pset_bind(2)

pset_create(2)

pset_destroy(2)

pset_getattr(2)

pset_info(2)

pset_list(2)

pset_setattr(2)

putacct(2)

putmsg(2)

putpmsg(2)

pwrite(2)

read(2)

readlink(2)

readlinkat(2)

readv(2)

rename(2)

renameat(2)

resolvepath(2)

rmdir(2)

sbrk(2)

semctl(2)

semget(2)

semids(2)

semop(2)

semtimedop(2)

setcontext(2)

setegid(2)

seteuid(2)

setgid(2)

setgroups(2)

setitimer(2)

setpflags(2)

setpgid(2)

setpgrp(2)

setppriv(2)

setrctl(2)

setregid(2)

setreuid(2)

setrlimit(2)

setsid(2)

settaskid(2)

setuid(2)

setustack(2)

shmadv(2)

shmat(2)

shmctl(2)

shmdt(2)

shmget(2)

shmids(2)

shmop(2)

sigaction(2)

sigaltstack(2)

sigpending(2)

sigprocmask(2)

sigsend(2)

sigsendset(2)

sigsuspend(2)

sigwait(2)

__sparc_utrap_install(2)

stat(2)

statvfs(2)

stime(2)

swapctl(2)

symlink(2)

symlinkat(2)

sync(2)

sysfs(2)

sysinfo(2)

time(2)

times(2)

uadmin(2)

ulimit(2)

umask(2)

umount(2)

umount2(2)

uname(2)

unlink(2)

unlinkat(2)

ustat(2)

utime(2)

utimensat(2)

utimes(2)

uucopy(2)

vfork(2)

vforkx(2)

vhangup(2)

waitid(2)

wracct(2)

write(2)

writev(2)

yield(2)

_lwp_cond_wait

, _lwp_cond_timedwait

, _lwp_cond_reltimedwait

- wait on a condition variable

Synopsis

#include <sys/lwp.h>int_lwp_cond_wait(lwp_cond_t *cvp,lwp_mutex_t *mp);
int_lwp_cond_timedwait(lwp_cond_t *cvp,lwp_mutex_t *mp,timestruc_t *abstime);
int_lwp_cond_reltimedwait(lwp_cond_t *cvp,lwp_mutex_t *mp,timestruc_t *reltime);

Description

These functions are used to wait for the occurrence of a conditionrepresented by an LWP condition variable. LWP condition variables must be initializedto 0 before use.

The_lwp_cond_wait() function atomically releases the LWP mutex pointed to bympand causes the calling LWP to block on the LWP condition variablepointed to bycvp. The blocked LWP may be awakened by_lwp_cond_signal(2),_lwp_cond_broadcast(2), or when interrupted by delivery of a signal. Any change invalue of a condition associated with the condition variable cannot be inferredby the return of_lwp_cond_wait() and any such condition must be re-evaluated.

The_lwp_cond_timedwait() function is similar to_lwp_cond_wait(), except that the calling LWPwill not block past the time of day specified byabstime. Ifthe time of day becomes greater thanabstime,_lwp_cond_timedwait() returns with theerror codeETIME.

The_lwp_cond_reltimedwait() function is similar to_lwp_cond_wait(), except that the calling LWPwill not block past the relative time specified byreltime. If thetime of day becomes greater than the starting time of day plusreltime,_lwp_cond_reltimedwait() returns with the error codeETIME.

The_lwp_cond_wait(),_lwp_cond_timedwait(), and_lwp_cond_reltimedwait() functions always return with the mutex lockedand owned by the calling lightweight process.

Return Values

Upon successful completion,0 is returned. A non-zero value indicates an error.

Errors

If any of the following conditions are detected,_lwp_cond_wait(),_lwp_cond_timedwait(), and_lwp_cond_reltimedwait()fail and return the corresponding value:

EINVAL

Thecvp argument points to an invalid LWP condition variable or themp argument points to an invalid LWP mutex.

EFAULT

Themp,cvp, orabstime argument points to an illegal address.

If any of the following conditions occur,_lwp_cond_wait(),_lwp_cond_timedwait(), and_lwp_cond_reltimedwait() failand return the corresponding value:

EINTR

The call was interrupted by a signal orfork(2).

If any of the following conditions occur,_lwp_cond_timedwait() and_lwp_cond_reltimedwait() fail andreturn the corresponding value:

ETIME

The time specified inabstime orreltime has passed.

Examples

Example 1 Use the_lwp_cond_wait() function in a loop testing some condition.

The_lwp_cond_wait() function is normally used in a loop testing some condition,as follows:

lwp_mutex_t m;lwp_cond_t cv;int cond;(void) _lwp_mutex_lock(&m);while (cond == FALSE) {        (void) _lwp_cond_wait(&cv, &m);}(void) _lwp_mutex_unlock(&m);

Example 2 Use the_lwp_cond_timedwait() function in a loop testing some condition.

The_lwp_cond_timedwait() function is also normally used in a loop testing somecondition. It uses an absolute timeout value as follows:

timestruc_t to;lwp_mutex_t m;lwp_cond_t cv;int cond, err;(void) _lwp_mutex_lock(&m);to.tv_sec = time(NULL) + TIMEOUT;to.tv_nsec = 0;while (cond == FALSE) {        err = _lwp_cond_timedwait(&cv, &m, &to);        if (err == ETIME) {                /* timeout, do something */                break;        SENDwhom}}(void) _lwp_mutex_unlock(&m);

This example sets a bound on the total wait time even thoughthe_lwp_cond_timedwait() may return several times due to the condition being signalledor the wait being interrupted.

Example 3 Use the_lwp_cond_reltimedwait() function in a loop testing some condition.

The_lwp_cond_reltimedwait() function is also normally used in a loop testing somecondition. It uses a relative timeout value as follows:

timestruc_t to;lwp_mutex_t m;lwp_cond_t cv;int cond, err;(void) _lwp_mutex_lock(&m);while (cond == FALSE) {        to.tv_sec = TIMEOUT;        to.tv_nsec = 0;        err = _lwp_cond_reltimedwait(&cv, &m, &to);        if (err == ETIME) {                /* timeout, do something */                break;        }}(void) _lwp_mutex_unlock(&m);

See Also

_lwp_cond_broadcast(2),_lwp_cond_signal(2),_lwp_kill(2),_lwp_mutex_lock(2),fork(2),kill(2)

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices
PreviousNext

[8]ページ先頭

©2009-2025 Movatter.jp