YIELD_TO(9) Driver Basics YIELD_TO(9)NAME
yield_to - yield the current processor to another thread in your thread group, or accelerate that thread toward the processor it's on.
SYNOPSIS
bool __sched yield_to(struct task_struct * p, bool preempt);
ARGUMENTS
p
target task
preempt
whether task preemption is allowed or not
DESCRIPTION
It's the caller's job to ensure that the target task struct can't go away on us before we can do any checks.
RETURN
true (>0) if we indeed boosted the target task. false (0) if we failed to boost the target. -ESRCH if there's no task to yield to.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 YIELD_TO(9)
Check Out this Related Man Page
iv_task(3) ivykis programmer's manual iv_task(3)NAME
iv_task_register, iv_task_unregister, iv_task_registered - deal with ivykis tasks
SYNOPSIS
#include <iv.h>
struct iv_task {
void *cookie;
void (*handler)(void *);
};
void IV_TASK_INIT(struct iv_task *task);
void iv_task_register(struct iv_task *task);
void iv_task_unregister(struct iv_task *task);
int iv_task_registered(struct iv_task *task);
DESCRIPTION
The functions iv_task_register and iv_task_unregister register, respectively unregister, a task with the current thread's ivykis event
loop. iv_task_registered on a task returns true if that task is currently registered with ivykis.
A task is like a timer, but with an immediate timeout. When a task is registered, unless it is unregistered again first, the callback
function specified by ->handler is guaranteed to be called once, in the thread that the task was registered in, some time after control
returns to the ivykis main loop but before ivykis will sleep for more events, with ->cookie as its first and sole argument. When this hap-
pens, the task is transparently unregistered.
Tasks are mainly used for scheduling code for execution where it is not appropriate to directly run that code in the calling context (for
example, because the current context might be run as a callback function where the caller expects certain conditions to remain invariant
after the callback completes).
The application is allowed to change the ->cookie and ->handler members at any time.
A given struct iv_task can only be registered in one thread at a time, and a task can only be unregistered in the thread that it was regis-
tered from.
There is no limit on the number of tasks registered at once.
See iv_examples(3) for programming examples.
SEE ALSO ivykis(3), iv_examples(3)ivykis 2010-08-15 iv_task(3)
Hi mates,
I am trying to copile and link to C programs with command:
cc file1,file2
but i raises the error "file not found" ... am i doing the right way?
any suggestion will be appreciated.
thanks
abdul (4 Replies)
Hi all,
using AWK iam sorting auniq data from a file the file size is 8GB, while running that script , the over all cpu usage will be nearly 8
how to avoid this ?? any other alternate is available for awk?
Thanks in Advance
Anish kumar.V (13 Replies)
Hi there,
Looking forward to your advice for the below:
I have a file which contains 2 paragraphs related to a particular pattern. I have to search for those paragraphs from a log file and then print a particular line from those paragraphs.
Sample:
I have one file with the fixed... (3 Replies)
Hi,
My OS is SunOS mymac1 5.10 Generic_148888-04 sun4v sparc SUNW,SPARC-Enterprise-T5220
When i cd /var/output
ls -ltr *.css
It yields the output in less than a second. While
find /var/output -type f -name "*.css"
does not complete for a while.
and
find /var/output -type f *.css... (13 Replies)