diff options
author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2010-07-25 14:29:11 +0300 |
---|---|---|
committer | Jens Axboe <jaxboe@fusionio.com> | 2010-08-07 18:53:16 +0200 |
commit | 6f904ff0e39ea88f81eb77e8dfb4e1238492f0a8 (patch) | |
tree | 8a22ff5ffe31e221554915ac9135da15d3adad8d /scripts/headers_install.pl | |
parent | 4aeefdc69f7b6f3f287e6fd8d4b213953b9e92d8 (diff) | |
download | blackbird-op-linux-6f904ff0e39ea88f81eb77e8dfb4e1238492f0a8.tar.gz blackbird-op-linux-6f904ff0e39ea88f81eb77e8dfb4e1238492f0a8.zip |
writeback: harmonize writeback threads naming
The write-back code mixes words "thread" and "task" for the same things. This
is not a big deal, but still an inconsistency.
hch: a convention I tend to use and I've seen in various places
is to always use _task for the storage of the task_struct pointer,
and thread everywhere else. This especially helps with having
foo_thread for the actual thread and foo_task for a global
variable keeping the task_struct pointer
This patch renames:
* 'bdi_add_default_flusher_task()' -> 'bdi_add_default_flusher_thread()'
* 'bdi_forker_task()' -> 'bdi_forker_thread()'
because bdi threads are 'bdi_writeback_thread()', so these names are more
consistent.
This patch also amends commentaries and makes them refer the forker and bdi
threads as "thread", not "task".
Also, while on it, make 'bdi_add_default_flusher_thread()' declaration use
'static void' instead of 'void static' and make checkpatch.pl happy.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'scripts/headers_install.pl')
0 files changed, 0 insertions, 0 deletions