Remove the spinlock protecting the pages allocation
Remove the spinlock protecting the pages allocation
The spinlock is taken in kcopyd_get_pages and kcopyd_put_pages.
kcopyd_get_pages is only called from run_pages_job, which is only
called from process_jobs called from do_work.
kcopyd_put_pages is called from client_alloc_pages (which is initialization
function) or from run_complete_job. run_complete_job is only called from
process_jobs called from do_work.
The spinlock is only taken on initialization or from single-threaded workqueue.
Therefore, the spinlock is useless.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
05-19-2011, 04:58 PM
Mikulas Patocka
Remove the spinlock protecting the pages allocation
Remove the spinlock protecting the pages allocation
The spinlock is taken in kcopyd_get_pages and kcopyd_put_pages.
kcopyd_get_pages is only called from run_pages_job, which is only
called from process_jobs called from do_work.
kcopyd_put_pages is called from client_alloc_pages (which is initialization
function) or from run_complete_job. run_complete_job is only called from
process_jobs called from do_work.
The spinlock is only taken on initialization or from single-threaded workqueue.
Therefore, the spinlock is useless.