Lines Matching full:job
14 is currently the sole consumer of padata's serialized job support.
16 Padata also supports multithreaded jobs, splitting up the job evenly while load
38 A padata_shell is used to submit a job to padata and allows a series of such
80 Running A Job
84 padata_priv structure, which represents one job::
99 The submission of the job is done with::
105 points to the preferred CPU to be used for the final callback when the job is
108 padata_do_parallel() is zero on success, indicating that the job is in
114 Each job submitted to padata_do_parallel() will, in turn, be passed to
123 parallel() will take responsibility for the job from this point. The job
125 outstanding, it should be prepared to be called again with a new job before
131 When a job does complete, parallel() (or whatever function actually finishes
159 A multithreaded job has a main thread and zero or more helper threads, with the
160 main thread participating in the job and then waiting until all helpers have
161 finished. padata splits the job into units called chunks, where a chunk is a
162 piece of the job that one thread completes in one call to the thread function.
164 A user has to do three things to run a multithreaded job. First, describe the
165 job by defining a padata_mt_job structure, which is explained in the Interface
167 call each time it assigns a job chunk to a thread. Then, define the thread
170 pointer to the job's shared state, if any. Prepare the shared state, which is
172 padata_do_multithreaded(), which will return once the job is finished.