Lines Matching refs:padata

4 The padata parallel execution mechanism
14 is currently the sole consumer of padata's serialized job support.
25 The first step in using padata to run serialized jobs is to set up a
28     #include <linux/padata.h>
34 Then, complete padata initialization by allocating a padata_shell::
38 A padata_shell is used to submit a job to padata and allows a series of such
72 user-supplied masks; these are the cpumasks padata actually uses.  So it is
73 legal to supply a cpumask to padata that contains offline CPUs.  Once an
74 offline CPU in the user-supplied cpumask comes online, padata is going to use
83 Actually submitting work to the padata instance requires the creation of a
88 	void                    (*parallel)(struct padata_priv *padata);
89 	void                    (*serial)(struct padata_priv *padata);
94 padata, but the structure should be zeroed at initialisation time, and the
102 		           struct padata_priv *padata, int *cb_cpu);
104 The ps and padata structures must be set up as described above; cb_cpu
122 Note that parallel() has no return value; the padata subsystem assumes that
132 the work) should inform padata of the fact with a call to::
134     void padata_do_serial(struct padata_priv *padata);
140 Note that this call may be deferred for a while since the padata code takes
147 Cleaning up a padata instance predictably involves calling the two free
161 finished.  padata splits the job into units called chunks, where a chunk is a
166 section.  This includes a pointer to the thread function, which padata will
177 .. kernel-doc:: include/linux/padata.h
178 .. kernel-doc:: kernel/padata.c