Lines Matching refs:padata

1 The padata parallel execution mechanism
8 those packets.  The crypto developers made a point of writing padata in a
11 The first step in using padata is to set up a padata_instance structure for
14     #include <linux/padata.h>
26 To allocate a padata instance with the cpu_possible_mask for both
34 user supplied cpumasks; these are the cpumasks padata actually uses. So
35 it is legal to supply a cpumask to padata that contains offline CPUs.
36 Once an offline CPU in the user supplied cpumask comes online, padata
47 padata cpumask contains no active CPU (flag not set).
48 padata_stop clears the flag and blocks until the padata instance
64 It's possible to change both cpumasks of a padata instance with
73 If a user is interested in padata cpumask changes, he can register to
74 the padata cpumask change notifier:
84 The padata cpumask change notifier notifies about changes of the usable
97 Actually submitting work to the padata instance requires the creation of a
102 	void                    (*parallel)(struct padata_priv *padata);
103 	void                    (*serial)(struct padata_priv *padata);
108 padata, but the structure should be zeroed at initialisation time, and the
116 		           struct padata_priv *padata, int cb_cpu);
118 The pinst and padata structures must be set up as described above; cb_cpu
135 Note that parallel() has no return value; the padata subsystem assumes that
140 whatever function actually finishes the job) should inform padata of the
143     void padata_do_serial(struct padata_priv *padata);
149 Note that this call may be deferred for a while since the padata code takes
153 The one remaining function in the padata API should be called to clean up
154 when a padata instance is no longer needed: