Lines Matching refs:padata

2 The padata parallel execution mechanism
11 those packets.  The crypto developers made a point of writing padata in a
14 The first step in using padata is to set up a padata_instance structure for
17     #include <linux/padata.h>
29 To allocate a padata instance with the cpu_possible_mask for both
37 user supplied cpumasks; these are the cpumasks padata actually uses. So
38 it is legal to supply a cpumask to padata that contains offline CPUs.
39 Once an offline CPU in the user supplied cpumask comes online, padata
50 padata cpumask contains no active CPU (flag not set).
51 padata_stop clears the flag and blocks until the padata instance
67 It's possible to change both cpumasks of a padata instance with
76 If a user is interested in padata cpumask changes, he can register to
77 the padata cpumask change notifier::
87 The padata cpumask change notifier notifies about changes of the usable
100 Actually submitting work to the padata instance requires the creation of a
105 	void                    (*parallel)(struct padata_priv *padata);
106 	void                    (*serial)(struct padata_priv *padata);
111 padata, but the structure should be zeroed at initialisation time, and the
119 		           struct padata_priv *padata, int cb_cpu);
121 The pinst and padata structures must be set up as described above; cb_cpu
138 Note that parallel() has no return value; the padata subsystem assumes that
143 whatever function actually finishes the job) should inform padata of the
146     void padata_do_serial(struct padata_priv *padata);
152 Note that this call may be deferred for a while since the padata code takes
156 The one remaining function in the padata API should be called to clean up
157 when a padata instance is no longer needed::