From: Nilay Shroff <nilay@linux.ibm.com>
To: Keith Busch <kbusch@meta.com>, linux-block@vger.kernel.org
Cc: axboe@kernel.org, ming.lei@redhat.com, chaitanyak@nvidia.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 0/4] block: make long runnint operations killable
Date: Fri, 23 Feb 2024 16:55:51 +0530 [thread overview]
Message-ID: <a17a6587-7565-46ee-a321-2ffce9ce7d86@linux.ibm.com> (raw)
In-Reply-To: <20240222191922.2130580-1-kbusch@meta.com>
On 2/23/24 00:49, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Changes from v2:
>
> Wait for chained bio's to complete before returning from kill signal.
>
> Miscellaneous cleanup patches for style and consistency.
>
> Keith Busch (4):
> block: blkdev_issue_secure_erase loop style
> block: cleanup __blkdev_issue_write_zeroes
> block: io wait hang check helper
> blk-lib: check for kill signal
>
> block/bio.c | 12 +----------
> block/blk-lib.c | 57 ++++++++++++++++++++++++++++++++++++++-----------
> block/blk-mq.c | 19 +++--------------
> block/blk.h | 13 +++++++++++
> 4 files changed, 61 insertions(+), 40 deletions(-)
>
I tried applying patchset using "git am" but it failed to apply. Was the patchset
created against the latest v6.8-rc5? Latter I applied the patchet manually.
I have tested the changes on my NVMe with ~1.5 TB capacity and verified that
the patch fixed the reported issue.
NVMe details:
# nvme id-ns /dev/nvme0n1 -H
NVME Identify Namespace 1:
nsze : 0x1749a956
ncap : 0x1749a956
nuse : 0x1749a956
<snip>
nvmcap : 1600321314816
<snip>
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use)
<snip>
# cat /sys/block/nvme0n1/queue/write_zeroes_max_bytes
8388608
# cat /sys/block/nvme0n1/queue/discard_granularity
4096
# cat /sys/block/nvme0n1/queue/discard_max_bytes
2199023255040
I tested following cases:
1) Zero-fill all sectors of NVMe using blkdiscard; While test is running
kill the 'blkdiscard' from other terminal and check the return status
# blkdiscars -z /dev/nvme0n1
Killed
# echo $?
137
2) Discard all sectors of NVMe using blkdiscard, While test is running kill
the 'blkdiscard' from other terminal
# blkdiscard /dev/nvme0n1
Killed
#echo $?
137
The bash return the status code 137 which signifies that 'blkdiscard' is killed.
My NVMe doesn't support secure erase operation so I couldn't test it.
# blkdiscard -s /dev/nvme0n1
blkdiscard: /dev/nvme0n1: BLKSECDISCARD ioctl failed: Operation not supported
Feel free to add:
Tested-by: Nilay Shroff<nilay@linux.ibm.com>
Thanks,
--Nilay
next prev parent reply other threads:[~2024-02-23 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 19:19 [PATCHv3 0/4] block: make long runnint operations killable Keith Busch
2024-02-22 19:19 ` [PATCHv3 1/4] block: blkdev_issue_secure_erase loop style Keith Busch
2024-02-23 3:22 ` Ming Lei
2024-02-23 6:41 ` Christoph Hellwig
2024-02-22 19:19 ` [PATCHv3 2/4] block: __blkdev_issue_write_zeroes cleanup Keith Busch
2024-02-23 3:29 ` Ming Lei
2024-02-23 6:42 ` Christoph Hellwig
2024-02-22 19:19 ` [PATCHv3 3/4] block: introduce io wait hang check helper Keith Busch
2024-02-23 3:31 ` Ming Lei
2024-02-23 6:43 ` Christoph Hellwig
2024-02-22 19:19 ` [PATCHv3 4/4] blk-lib: check for kill signal Keith Busch
2024-02-23 3:38 ` Ming Lei
2024-02-23 6:46 ` Christoph Hellwig
2024-02-23 11:00 ` Nilay Shroff
2024-02-23 15:58 ` Keith Busch
2024-02-23 11:25 ` Nilay Shroff [this message]
2024-02-23 15:57 ` [PATCHv3 0/4] block: make long runnint operations killable Keith Busch
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=a17a6587-7565-46ee-a321-2ffce9ce7d86@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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 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.