public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Wang <nwang@suse.com>
To: nwang@suse.com
Cc: philipp.reisner@linbit.com,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org
Subject: [Patch v2 06/10] drbd: Wapper for zeroing out device by worker
Date: Mon, 13 Jul 2015 16:39:00 +0800	[thread overview]
Message-ID: <1436776744-3135-7-git-send-email-nwang@suse.com> (raw)
In-Reply-To: <1436776744-3135-1-git-send-email-nwang@suse.com>

Wapper functions for drbd_device_post_work to start
zeroing out device. Change state when both node
finish zeroing.

Signed-off-by: Nick Wang <nwang@suse.com>
CC: Philipp Reisner <philipp.reisner@linbit.com>
CC: Lars Ellenberg <lars.ellenberg@linbit.com>
CC: drbd-dev@lists.linbit.com
CC: linux-kernel@vger.kernel.org
---
 drbd/drbd_int.h    |  2 ++
 drbd/drbd_worker.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 65 insertions(+)

diff --git a/drbd/drbd_int.h b/drbd/drbd_int.h
index f43f957..dd680a9 100644
--- a/drbd/drbd_int.h
+++ b/drbd/drbd_int.h
@@ -1670,6 +1670,8 @@ extern bool drbd_rs_c_min_rate_throttle(struct drbd_device *device);
 extern bool drbd_rs_should_slow_down(struct drbd_device *device, sector_t sector,
 		bool throttle_if_app_is_waiting);
 extern int zero_out_local_device(struct drbd_device *device);
+extern void require_zero_out_local_device(struct drbd_device *device);
+extern void receive_zero_out_local_device(struct drbd_device *device);
 extern int drbd_submit_peer_request(struct drbd_device *,
 				    struct drbd_peer_request *, const unsigned,
 				    const int);
diff --git a/drbd/drbd_worker.c b/drbd/drbd_worker.c
index 50564f5..293aa27 100644
--- a/drbd/drbd_worker.c
+++ b/drbd/drbd_worker.c
@@ -1674,6 +1674,69 @@ int zero_out_local_device(struct drbd_device *device)
 		device->ldev->known_size, GFP_NOIO, false);
 }
 
+/**
+ * require_zero_out_local_device()
+ * @device: DRBD device.
+ *
+ * Description:
+ * Start to zero out local device. Update
+ * status if peer node (secondary) finished
+ * zeroing.
+ *
+**/
+void require_zero_out_local_device(struct drbd_device *device)
+{
+	int zero_out_err = 0;
+
+	zero_out_err = zero_out_local_device(device);
+
+	if (zero_out_err) {
+		drbd_err(device, "Failed to zero out local device\n");
+		set_bit(ZERO_FAIL, &device->flags);
+		drbd_chk_io_error(device, 1, DRBD_WRITE_ERROR);
+	} else {
+		drbd_info(device, "Finished zero out local device.\n");
+
+		if (test_and_clear_bit(ZERO_DONE, &device->flags)) {
+			spin_lock_irq(&device->resource->req_lock);
+			_drbd_set_state(_NS2(device, disk, D_UP_TO_DATE,
+				pdsk, D_UP_TO_DATE), CS_VERBOSE, NULL);
+			spin_unlock_irq(&device->resource->req_lock);
+			drbd_send_zero_out_finish(first_peer_device(device));
+		} else if (test_and_clear_bit(ZERO_FAIL, &device->flags)) {
+			drbd_info(device, "Peer device has already failed on zero out\n");
+		} else {
+			/* waiting for peer device finished */
+			set_bit(ZERO_DONE, &device->flags);
+		}
+	}
+}
+
+/**
+ * receive_zero_out_local_device()
+ * @device: DRBD device.
+ *
+ * Description:
+ * Start to zero out local device.
+ * Notify peer node the zeroing result.
+ *
+**/
+void receive_zero_out_local_device(struct drbd_device *device)
+{
+	int zero_out_err = 0;
+	struct drbd_peer_device *const peer_device = first_peer_device(device);
+
+	zero_out_err = zero_out_local_device(device);
+	if (zero_out_err) {
+		drbd_err(device, "Failed to zero out local device\n");
+		drbd_send_zero_out_fail(peer_device);
+		drbd_chk_io_error(device, 1, DRBD_WRITE_ERROR);
+	} else {
+		drbd_info(device, "Finished zero out local device.\n");
+		drbd_send_zero_out_ok(peer_device);
+	}
+}
+
 void start_resync_timer_fn(unsigned long data)
 {
 	struct drbd_device *device = (struct drbd_device *) data;
-- 
1.8.4.5


  parent reply	other threads:[~2015-07-13  8:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  8:38 [Patch v2 00/10] Zero out devices instead of initial full sync Nick Wang
2015-07-13  8:38 ` [Patch v2 01/10] drbd: Fix the wrong logic of moving history Nick Wang
2015-07-13  8:38 ` [Patch v2 02/10] drbd: Add option zap_devices to new-current-uuid Nick Wang
2015-07-31 12:50   ` [Drbd-dev] " Philipp Reisner
2015-07-13  8:38 ` [Patch v2 03/10] drbd: A function to zero out drbd backing device Nick Wang
2015-07-13  8:38 ` [Patch v2 04/10] drbd: New packet P_ZERO_OUT Nick Wang
2015-07-13  8:38 ` [Patch v2 05/10] drbd: Functions to notify peer node to zero out Nick Wang
2015-07-13  8:39 ` Nick Wang [this message]
2015-07-13  8:39 ` [Patch v2 07/10] drbd: Flags for background drbd device work Nick Wang
2015-07-13  8:39 ` [Patch v2 08/10] drbd: Function to work with packet P_ZERO_OUT Nick Wang
2015-07-13  8:39 ` [Patch v2 09/10] drbd: Handle zero out command from peer node Nick Wang
2015-07-13  8:39 ` [Patch v2 10/10] drbd: Handle new-current-uuid --zap-devices Nick Wang
2015-07-31 12:48 ` [Drbd-dev] [Patch v2 00/10] Zero out devices instead of initial full sync Philipp Reisner
2015-08-06 10:04   ` [PATCH v3 0/1] Zeroout/discard " Nick Wang
2015-08-06 10:04     ` [PATCH] drbd: Support zeroout device " Nick Wang
2015-08-18 15:03       ` Lars Ellenberg
2015-08-21  3:26         ` 答复: " Nick Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436776744-3135-7-git-send-email-nwang@suse.com \
    --to=nwang@suse.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox