--class contains which stressors

[yumdeer]

hi

I found that --class seems to be parsed from xx.job (maybe it wrong), but I did not find the corresponding parsing method, and I did not find the corresponding os.job for --class os.

If anyone can give me an answer, I would be very grateful.

[ColinIanKing]

There aren't any os.job examples, I'll get around to adding them before the next release in September 2024.

[ColinIanKing]

Note one list the stressors that belong to the os class by using the following:

stress-ng --class os?
class 'os' stressors: access acl af-alg aio aiol alarm apparmor bad-altstack bad-ioctl bigheap binderfs bind-mount brk cap cgroup chattr chdir chmod chown chroot clock clone close copy-file cpu-online cyclic daemon dccp dentry dev dev-shm dir dirdeep dirmany dnotify dup dynlib efivar enosys env epoll eventfd exec exit-group fallocate fanotify fault fcntl fd-fork fd-race fiemap fifo file-ioctl filename flock fork forkheavy fpunch fsize fstat full futex get getdent getrandom handle hdd icmp-flood idle-page inode-flags inotify io iomix ioprio io-uring itimer kcmp key kill klog kvm landlock lease led link loadavg locka lockf lockofd loop lsm madvise malloc memfd memhotplug metamix mincore min-nanosleep mknod mlock mlockmany mmap mmapaddr mmapfiles mmapfixed mmapfork mmaphuge mmapmany module mprotect mq mremap mseal msg msync msyncmany mtx munmap mutex nanosleep netlink-proc netlink-task nice null numa oom-pipe opcode open pagemove pageswap pci personality pidfd ping-sock pipe pipeherd pkey plugin poll prctl prio-inv procfs pthread ptrace pty quota race-sched ramfs rawpkt rawsock rawudp readahead reboot remap rename resched resources revio ring-pipe rlimit rmap rtc schedmix schedpolicy seal seccomp seek sem sem-sysv sendfile session set shm shm-sysv sigabrt sigbus sigchld sigfd sigfpe sigio sigill signal signest sigpending sigpipe sigq sigrt sigsegv sigsuspend sigtrap sigurg sigvtalrm sigxcpu sigxfsz sleep sock sockabuse sockdiag sockfd sockmany sockpair spawn splice statmount swap switch symlink sync-file sysbadaddr syscall sysfs sysinfo sysinval tee timer timerfd time-warp tlb-shootdown tmpfs touch tun udp udp-flood umount unlink unshare urandom userfaultfd usersyscall utime vdso verity vfork vforkmany vm vm-addr vm-rw vm-segv vm-splice wait watchdog workload x86syscall xattr yield zero zombie

[yumdeer]

Thank you for your help.

Then I seem to understand that the idea that class xx.module is parsed from xx.job is wrong, because now the program can be called through class os, but os.job is not implemented. I re-read the code, and it seems that the corresponding CLASS_XX macro is configured from the struct member .class corresponding to each .c, and then judged bit by bit. (ps. stressors[j].info->class & cl)

If possible, can you tell me whether my judgment is accurate? maybe can give me some guidance How does the code determine which stressors belong to which class? Thanks

[ColinIanKing]

To see which stressors belong a class add a question mark, e.g. for the os class, use:

stress-ng --class os?