Lines Matching refs:be

4 Padata is a mechanism by which the kernel can farm work out to be done in
6 developed for use with the IPsec code, which needs to be able to perform
9 sufficiently general fashion that it could be put to other uses as well.
12 overall control of how tasks are to be run:
20 The pcpumask describes which processors will be used to execute work
22 processors are allowed to be used as the serialization callback processor.
23 The workqueue wq is where the work will actually be done; it should be
27 cpumasks this helper function can be used:
51 The list of CPUs to be used can be adjusted with these functions:
61 Changing the CPU masks are expensive operations, though, so it should not be
106 This structure will almost certainly be embedded within some larger
107 structure specific to the work to be done.  Most of its fields are private to
108 padata, but the structure should be zeroed at initialisation time, and the
109 parallel() and serial() functions should be provided.  Those functions will
110 be called in the process of getting the work done as we will see
118 The pinst and padata structures must be set up as described above; cb_cpu
119 specifies which CPU will be used for the final callback when the work is
120 done; it must be in the current instance's CPU mask.  The return value from
126 Each task submitted to padata_do_parallel() will, in turn, be passed to
132 information about the actual work to be done is probably obtained by using
137 need not be completed during this call, but, if parallel() leaves work
138 outstanding, it should be prepared to be called again with a new job before
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
159 might be best not to call it while there is work outstanding.  Shutting
160 down the workqueue, if necessary, should be done separately.