On Tue, Nov 27, 2018 at 08:50:08PM +0100, Pavel Machek wrote: > Hi! Hi, Pavel. > > +============================================ > > +ktask: parallelize CPU-intensive kernel work > > +============================================ > > + > > +:Date: November, 2018 > > +:Author: Daniel Jordan <daniel.m.jordan@xxxxxxxxxx> > > > > +For example, consider the task of clearing a gigantic page. This used to be > > +done in a single thread with a for loop that calls a page clearing function for > > +each constituent base page. To parallelize with ktask, the client first moves > > +the for loop to the thread function, adapting it to operate on the range passed > > +to the function. In this simple case, the thread function's start and end > > +arguments are just addresses delimiting the portion of the gigantic page to > > +clear. Then, where the for loop used to be, the client calls into ktask with > > +the start address of the gigantic page, the total size of the gigantic page, > > +and the thread function. Internally, ktask will divide the address range into > > +an appropriate number of chunks and start an appropriate number of threads to > > +complete these chunks. > > Great, so my little task is bound to CPUs 1-4 and uses gigantic > pages. Kernel clears them for me. > > a) Do all the CPUs work for me, or just CPUs I was assigned to? In ktask's current form, all the CPUs. This is an existing limitation of workqueues, which ktask is built on: unbound workqueue workers don't honor the cpumask of the queueing task (...absent a wq user applying a cpumask wq attr beforehand, which nobody in-tree does...). But good point, the helper threads should only run on the CPUs the task is bound to. I'm working on cgroup-aware workqueues but hadn't considered a task's cpumask outside of cgroup/cpuset, so I'll try adding support for this too. > b) Will my time my_little_task show the system time including the > worker threads? No, system time of kworkers isn't accounted to the user tasks they're working on behalf of. This time is already visible to userland in kworkers, and it would be confusing to account it to a userland task instead. Thanks for the questions. Daniel
