Searched hist:"70 df7092" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/drivers/block/drbd/ |
H A D | drbd_nl.c | 70df7092 Fri Dec 20 04:17:02 CST 2013 Lars Ellenberg <lars.ellenberg@linbit.com> drbd: allow write-ordering policy to be bumped up again
Previously, once you disabled flushes as a means of enforcing write-ordering, you'd need to detach/re-attach to enable them again.
Allow drbdsetup disk-options to re-enable previously disabled write-ordering policy options at runtime.
While at it fix RCU in drbd_bump_write_ordering() max_allowed_wo() uses rcu_dereference, therefore it must be called within rcu_read_lock()/rcu_read_unlock()
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com> 70df7092 Fri Dec 20 04:17:02 CST 2013 Lars Ellenberg <lars.ellenberg@linbit.com> drbd: allow write-ordering policy to be bumped up again Previously, once you disabled flushes as a means of enforcing write-ordering, you'd need to detach/re-attach to enable them again. Allow drbdsetup disk-options to re-enable previously disabled write-ordering policy options at runtime. While at it fix RCU in drbd_bump_write_ordering() max_allowed_wo() uses rcu_dereference, therefore it must be called within rcu_read_lock()/rcu_read_unlock() Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
|
H A D | drbd_receiver.c | 70df7092 Fri Dec 20 04:17:02 CST 2013 Lars Ellenberg <lars.ellenberg@linbit.com> drbd: allow write-ordering policy to be bumped up again
Previously, once you disabled flushes as a means of enforcing write-ordering, you'd need to detach/re-attach to enable them again.
Allow drbdsetup disk-options to re-enable previously disabled write-ordering policy options at runtime.
While at it fix RCU in drbd_bump_write_ordering() max_allowed_wo() uses rcu_dereference, therefore it must be called within rcu_read_lock()/rcu_read_unlock()
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com> 70df7092 Fri Dec 20 04:17:02 CST 2013 Lars Ellenberg <lars.ellenberg@linbit.com> drbd: allow write-ordering policy to be bumped up again Previously, once you disabled flushes as a means of enforcing write-ordering, you'd need to detach/re-attach to enable them again. Allow drbdsetup disk-options to re-enable previously disabled write-ordering policy options at runtime. While at it fix RCU in drbd_bump_write_ordering() max_allowed_wo() uses rcu_dereference, therefore it must be called within rcu_read_lock()/rcu_read_unlock() Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
|