Oracle Solaris 9 线程与实时库函数手册

需积分: 5 50 浏览量更新于2024-06-22 收藏 1.2MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Oracle Solaris 9 的 man pages 部分 3 主要涵盖了线程和实时库函数，这是操作系统开发和高级编程中的关键组件。文档由 Sun Microsystems 出版，提供了关于如何在 Oracle Solaris 9 上利用线程和实时功能的详细指南。这些函数允许开发者创建高效、响应迅速的多线程应用程序，适应高并发和实时需求的环境。" Oracle Solaris 9 的 man pages 是一组详尽的参考手册，其中的 Section 3 特别关注线程（Threads）和实时（Realtime）库函数。线程是现代操作系统中的基本执行单元，它允许在一个进程中同时运行多个并发执行的流，提高了系统的资源利用率和性能。在 Oracle Solaris 9 中，线程库提供了丰富的 API，如 `pthread_create` 用于创建新线程，`pthread_join` 用于等待线程结束，以及 `pthread_mutex_lock` 和 `pthread_mutex_unlock` 用于线程同步和互斥访问共享资源。实时库函数则专注于提供低延迟和确定性的系统服务，这对于那些需要快速响应和严格时间约束的应用程序至关重要，例如金融交易系统、工业自动化和多媒体应用。这些函数包括定时器操作、优先级调度等，例如 `clock_gettime` 用于获取精确的时间，`nice` 和 `setpriority` 可以调整线程或进程的优先级。文档还可能包含线程安全（thread-safe）函数的描述，这些函数可以在多线程环境中被安全地调用，不会因为其他线程的操作而产生未定义的行为。此外，它还可能涉及信号处理、线程属性设置、条件变量、读写锁等高级主题。在 Oracle Solaris 9 中，开发者可以利用高级特性如 LWP（轻量级进程，Lightweight Processes），这是系统实现线程的方式，它们共享相同的地址空间，但拥有独立的调度实体。LWP 提供了线程级的并行性和调度灵活性，使得多线程应用程序能够充分利用多处理器系统的优势。文档还可能涉及到错误处理和调试技巧，帮助开发者解决在实现线程和实时功能时遇到的问题。例如，使用 `pthread_error` 检查返回代码，以及使用特定的调试工具和标志来追踪线程行为和系统资源的使用。 Oracle Solaris 9 的 man pages section 3 是一个宝贵的资源，它详细阐述了如何在该操作系统上进行线程编程和实现实时功能，对于系统管理员、软件开发者以及对 Solaris 内核有深入兴趣的人来说都是必不可少的参考资料。

资源详情

资源推荐

aiocancel – cancel an asynchronous operation

cc [ ﬂag ... ] ﬁle ... -laio [ library ... ]

#include <sys/asynch.h>

int aiocancel(aio_result_t *resultp);

aiocancel() cancels the asynchronous operation associated with the result buffer

pointed to by resultp. It may not be possible to immediately cancel an operation which

is in progress and in this case, aiocancel() will not wait to cancel it.

Upon successful completion, aiocancel() returns 0 and the requested operation is

cancelled. The application will not receive the SIGIO completion signal for an

asynchronous operation that is successfully cancelled.

Upon successful completion, aiocancel() returns 0. Upon failure, aiocancel()

returns −1 and sets errno to indicate the error.

aiocancel() will fail if any of the following are true:

EACCES The parameter resultp does not correspond to any outstanding

asynchronous operation, although there is at least one currently

outstanding.

EFAULT resultp points to an address outside the address space of the

requesting process. See NOTES.

EINVAL There are not any outstanding requests to cancel.

See attributes (5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE

MT-Level Safe

aioread(3AIO), aiowait(3AIO), attributes(5)

Passing an illegal address as resultp will result in setting errno to EFAULT only if it is

detected by the application process.

aiocancel(3AIO)

NAME

SYNOPSIS

DESCRIPTION

RETURN VALUES

ERRORS

ATTRIBUTES

SEE ALSO

NOTES

16 man pages section 3: Threads and Realtime Library Functions • Last Revised 5 Mar 1997

aio_cancel – cancel asynchronous I/O request

cc [ ﬂag... ] ﬁle... -lrt [ library... ]

#include <aio.h>

int aio_cancel(int ﬁldes, struct aiocb *aiocbp);

The aio_cancel() function attempts to cancel one or more asynchronous I/O

requests currently outstanding against ﬁle descriptor ﬁldes. The aiocbp argument points

to the asynchronous I/O control block for a particular request to be canceled. If aiocbp

is NULL, then all outstanding cancelable asynchronous I/O requests against ﬁldes are

canceled.

Normal asynchronous notiﬁcation occurs for asynchronous I/O operations that are

successfully canceled. If there are requests that cannot be canceled, then the normal

asynchronous completion process takes place for those requests when they are

completed.

For requested operations that are successfully canceled, the associated error status is

set to ECANCELED and the return status is −1. For requested operations that are not

successfully canceled, the aiocbp is not modiﬁed by aio_cancel().

If aiocbp is not NULL, then if ﬁldes does not have the same value as the ﬁle descriptor

with which the asynchronous operation was initiated, unspeciﬁed results occur.

The aio_cancel() function returns the value AIO_CANCELED to the calling process

if the requested operation(s) were canceled. The value AIO_NOTCANCELED is returned

if at least one of the requested operation(s) cannot be canceled because it is in

progress. In this case, the state of the other operations, if any, referenced in the call to

aio_cancel() is not indicated by the return value of aio_cancel(). The

application may determine the state of affairs for these operations by using

aio_error(3RT). The value AIO_ALLDONE is returned if all of the operations have

already completed. Otherwise, the function returns −1 and sets errno to indicate the

error.

The aio_cancel() function will fail if:

EBADF The ﬁldes argument is not a valid ﬁle descriptor.

ENOSYS The aio_cancel() function is not supported.

The aio_cancel() function has a transitional interface for 64-bit ﬁle offsets. See

lf64(5).

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE

MT-Level MT-Safe

aio_cancel(3RT)

NAME

SYNOPSIS

DESCRIPTION

RETURN VALUES

ERRORS

USAGE

ATTRIBUTES

Threads and Realtime Library Functions 17

aio_error – retrieve errors status for an asynchronous I/O operation

cc [ ﬂag... ] ﬁle... -lrt [ library... ]

#include <aio.h>

int aio_error(const struct aiocb *aiocbp);

The aio_error() function returns the error status associated with the aiocb

structure referenced by the aiocbp argument. The error status for an asynchronous I/O

operation is the errno value that would be set by the corresponding read(2),

write(2), or fsync(3C) operation. If the operation has not yet completed, then the

error status will be equal to EINPROGRESS.

If the asynchronous I/O operation has completed successfully, then 0 is returned. If

the asynchronous operation has completed unsuccessfully, then the error status, as

described for read(2), write(2), and fsync(3C), is returned. If the asynchronous I/O

operation has not yet completed, then EINPROGRESS is returned.

The aio_error() function will fail if:

ENOSYS The aio_error() function is not supported by the system.

The aio_error() function may fail if:

EINVAL The aiocbp argument does not refer to an asynchronous operation

whose return status has not yet been retrieved.

The aio_error() function has a transitional interface for 64-bit ﬁle offsets. See

lf64(5).

EXAMPLE 1 The following is an example of an error handling routine using the

aio_error() function.

#include <aio.h>

#include <errno.h>

#include <signal.h>

struct aiocb my_aiocb;

struct sigaction my_sigaction;

void my_aio_handler(int, siginfo_t *, void *);

...

my_sigaction.sa_flags = SA_SIGINFO;

my_sigaction.sa_sigaction = my_aio_handler;

sigemptyset(&my_sigaction.sa_mask);

(void) sigaction(SIGRTMIN, &my_sigaction, NULL);

...

my_aiocb.aio_sigevent.sigev_notify = SIGEV_SIGNAL;

my_aiocb.aio_sigevent.sigev_signo = SIGRTMIN;

my_aiocb.aio_sigevent.sigev_value.sival_ptr = &myaiocb;

...

(void) aio_read(&my_aiocb);

...

void

my_aio_handler(int signo, siginfo_t *siginfo, void *context) {

int my_errno;

struct aiocb *my_aiocbp;

aio_error(3RT)

NAME

SYNOPSIS

DESCRIPTION

RETURN VALUES

ERRORS

USAGE

EXAMPLES

Threads and Realtime Library Functions 19

剩余325页未读，继续阅读

weixin_40191861_zj

粉丝: 67
资源: 1万+

会员权益专享

Oracle Solaris 9 线程与实时库函数手册

Oracle Solaris 9 -man pages section 3: Threads and Realtime Libr

Oracle Solaris 8 man pages section 3: Threads and Realtime Libr

817-3944.pdf Oracle Solaris 9 - man pages section 3: Threads and

软件测试-Jmeter性能测试实战：Jmeter分布式测试的搭建和优化

软件测试-Jmeter性能测试实战：命令行操作技巧与持续集成实践

软件测试-Jmeter性能测试实战：使用Jmeter实现接口负载测试的技巧

server: port: 8082 forward-headers-strategy: true undertow: io-threads: 2 worker-threads: 36 buffer-size: 1024 directBuffers: true servlet: session: timeout: 86400

/usr/bin/ld: cannot find -lThreads::Threads collect2: error: ld returned 1 exit status

undertow: url-charset: utf-8 threads: io: 8 worker: 256

2023-06-12 09:15:34,884 - numexpr.utils - INFO - Note: NumExpr detected 24 cores but "NUMEXPR_MAX_THREADS" not set, so enforcing safe limit of 8. 2023-06-12 09:15:34,884 - numexpr.utils - INFO - NumExpr defaulting to 8 threads.如何解决

2023-06-11 23:29:18,030 - numexpr.utils - INFO - Note: NumExpr detected 24 cores but "NUMEXPR_MAX_THREADS" not set, so enforcing safe limit of 8. 2023-06-11 23:29:18,030 - numexpr.utils - INFO - NumExpr defaulting to 8 threads.

解释 server: tomcat: uri-encoding: UTF-8 threads: max: 200 min-spare: 30 connection-timeout: 5000ms port: 8080 servlet: context-path: /Csdn-api

--flat=false --split-count=2 --retries=6 --threads=6 Linux命令解析

sudo ./t-rex-64 -i 无状态模式下，正确的打印消息是什么样的

会员权益专享

最新资源