diff options
| author | Lars Ellenberg <lars.ellenberg@linbit.com> | 2014-03-18 12:30:09 +0100 |
|---|---|---|
| committer | Philipp Reisner <philipp.reisner@linbit.com> | 2014-07-10 18:35:00 +0200 |
| commit | aaaba34576407857f6146ff6c330f06e63fb2bf2 (patch) | |
| tree | 6cd468ecb123314d06c641185410f6cbce58c504 /ipc | |
| parent | drbd: don't implicitly resize Diskless node beyond end of device (diff) | |
| download | linux-aaaba34576407857f6146ff6c330f06e63fb2bf2.tar.xz linux-aaaba34576407857f6146ff6c330f06e63fb2bf2.zip | |
drbd: implement csums-after-crash-only
Checksum based resync trades CPU cycles for network bandwidth,
in situations where we expect much of the to-be-resynced blocks
to be actually identical on both sides already.
In a "network hickup" scenario, it won't help:
all to-be-resynced blocks will typically be different.
The use case is for the resync of *potentially* different blocks
after crash recovery -- the crash recovery had marked larger areas
(those covered by the activity log) as need-to-be-resynced,
just in case. Most of those blocks will be identical.
This option makes it possible to configure checksum based resync,
but only actually use it for the first resync after primary crash.
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions