For user-initiated threads like ll_sa_* these should be associated with the UID/GID/PID of the original task for %u, %g, and %p, so that they can be accounted correctly on the servers.

For jobid_name_is_valid() we may consider to reduce the exclusions for kernel processes. Firstly, this exclusion doesn't always working properly, since kworker and ll_sa tasks still show up in the server stats. Secondly, this hides the real presence of RPCs sent to the server, so job_stats are not showing the full picture of what is generating the load.

The client needs to save the originating comm/UID/GID/PID for the work that is done (e.g. cache in inode when it is read/written). This should already be happening, but doesn't seem to be used consistently.