Updated: April 19, 2023 |
Support pathconf() requests
#include <sys/iofunc.h> int iofunc_pathconf( resmgr_context_t *ctp, io_pathconf_t *msg, iofunc_ocb_t *ocb, iofunc_attr_t *attr );
libc
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The iofunc_pathconf() helper function does what's needed to support pathconf() with the mount and attr passed to it. Other fsys pathconf() requests need to be handled by the caller.
If you write your own pathconf callout for your resource manager, use the following macro to pass the requested value back to the caller:
_IO_SET_PATHCONF_VALUE( resmgr_context_t *ctp, int value )
io_pathconf_t structure
The io_pathconf_t structure holds the _IO_PATHCONF message received by the resource manager:
struct _io_pathconf { uint16_t type; uint16x_t combine_len; short name; uint16_t zero; }; typedef union { struct _io_pathconf i; /* value is returned with MsgReply */ } io_pathconf_t;
The I/O message structures are unions of an input message (coming to the resource manager) and an output or reply message (going back to the client). In this case, there's only an input message, i.
The i member is a structure of type _io_pathconf that contains the following members:
EOK, or _RESMGR_DEFAULT if the function didn't handle the pathconf() request.
Safety: | |
---|---|
Cancellation point | No |
Interrupt handler | No |
Signal handler | Yes |
Thread | Yes |