All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Haberland <sth@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
	Jan Hoeppner <hoeppner@linux.ibm.com>,
	linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [PATCH 0/7] s390/dasd: add dasd autoquiesce feature
Date: Wed,  5 Apr 2023 16:20:10 +0200	[thread overview]
Message-ID: <20230405142017.2446986-1-sth@linux.ibm.com> (raw)

Hi Jens,

please apply the following patchset that introduces an
autoquiesce feature for DASD devices.

Quiesce and resume are functions that tell Linux to stop/resume
issuing I/Os to a specific DASD.
The DASD driver allows a manual quiesce/resume via ioctl.

Autoquiesce will define an amount of triggers that will lead to
an automatic quiesce if a certain event occurs.
There is no automatic resume.

The autoquiesce feature is useful for devices in a copy relation
where different events should lead to an automatic quiesce of a
device. This prevents IO errors, unnecessary load and gives the
controlling agent time to sort out the situation and trigger a swap
of copy pairs if needed before it will resume device operation.

Stefan Haberland (7):
  s390/dasd: remove unused DASD EER defines
  s390/dasd: add autoquiesce feature
  s390/dasd: add aq_mask sysfs attribute
  s390/dasd: add aq_requeue sysfs attribute
  s390/dasd: add aq_timeouts autoquiesce trigger
  s390/dasd: add autoquiesce event for start IO error
  s390/dasd: fix hanging blockdevice after request requeue

 arch/s390/include/uapi/asm/dasd.h |   2 +
 drivers/s390/block/dasd.c         |  75 +++++++++++++-----
 drivers/s390/block/dasd_devmap.c  | 126 ++++++++++++++++++++++++++++++
 drivers/s390/block/dasd_eckd.c    |   1 +
 drivers/s390/block/dasd_eer.c     |   1 +
 drivers/s390/block/dasd_int.h     |  32 ++++----
 6 files changed, 204 insertions(+), 33 deletions(-)

-- 
2.37.2


             reply	other threads:[~2023-04-05 14:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 14:20 Stefan Haberland [this message]
2023-04-05 14:20 ` [PATCH 1/7] s390/dasd: remove unused DASD EER defines Stefan Haberland
2023-04-12  1:31   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 2/7] s390/dasd: add autoquiesce feature Stefan Haberland
2023-04-12  1:33   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 3/7] s390/dasd: add aq_mask sysfs attribute Stefan Haberland
2023-04-12  1:33   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 4/7] s390/dasd: add aq_requeue " Stefan Haberland
2023-04-12  1:34   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 5/7] s390/dasd: add aq_timeouts autoquiesce trigger Stefan Haberland
2023-04-12  1:34   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 6/7] s390/dasd: add autoquiesce event for start IO error Stefan Haberland
2023-04-12  1:35   ` Halil Pasic
2023-04-05 14:20 ` [PATCH 7/7] s390/dasd: fix hanging blockdevice after request requeue Stefan Haberland
2023-04-12  1:35   ` Halil Pasic
2023-04-12  1:53 ` [PATCH 0/7] s390/dasd: add dasd autoquiesce feature Jens Axboe

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=20230405142017.2446986-1-sth@linux.ibm.com \
    --to=sth@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.