From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Xiao Ni <xni@redhat.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-raid@vger.kernel.org, Jes Sorensen <jes@trained-monkey.org>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
Coly Li <colyli@suse.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Jonmichael Hands <jm@chia.net>,
Stephen Bates <sbates@raithlin.com>,
Martin Oliveira <Martin.Oliveira@eideticom.com>,
David Sloan <David.Sloan@eideticom.com>
Subject: Re: [PATCH mdadm v4 0/7] Write Zeroes option for Creating Arrays
Date: Tue, 25 Oct 2022 22:41:50 -0400 [thread overview]
Message-ID: <yq1tu3rtio1.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CALTww28XKzYmKrVQn=yYyq3xpjcEDzz1Bao+eLx3LR5mbm333Q@mail.gmail.com> (Xiao Ni's message of "Thu, 13 Oct 2022 15:51:12 +0800")
Xiao,
> If the upper layer submit 1GB request, SCSI will split them and handle
> 32MB requests in default. If the upper layer wants SCSI to handle 1GB
> one time, it needs to pass some information to SCSI, right?
It is the device that defines its capabilities, not Linux. If the device
states it wants 32MB per request, then that's what we'll issue.
>> In NVMe there's a limit of 64K blocks per range and 256 ranges per
>> request. So 8GB or 64GB per request for discard depending on the block
>> size. So presumably it will take several operations to deallocate an
>> entire drive.
>
> Could you tell the command how to check the block size.
> blockdev --getsz tells the sector size of the device. It should not be the
> block size you mentioned here.
blockdev --getss will tell you the device's logical block size.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-10-26 2:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 20:10 [PATCH mdadm v4 0/7] Write Zeroes option for Creating Arrays Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 1/7] Create: goto abort_locked instead of return 1 in error path Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 2/7] Create: remove safe_mode_delay local variable Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 3/7] Create: Factor out add_disks() helpers Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 4/7] mdadm: Introduce pr_info() Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 5/7] mdadm: Add --write-zeros option for Create Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 6/7] tests/00raid5-zero: Introduce test to exercise --write-zeros Logan Gunthorpe
2022-10-07 20:10 ` [PATCH mdadm v4 7/7] manpage: Add --write-zeroes option to manpage Logan Gunthorpe
2022-10-12 1:09 ` [PATCH mdadm v4 0/7] Write Zeroes option for Creating Arrays Xiao Ni
2022-10-12 16:59 ` Logan Gunthorpe
2022-10-13 1:33 ` Martin K. Petersen
2022-10-13 7:51 ` Xiao Ni
2022-10-26 2:41 ` Martin K. Petersen [this message]
2022-10-27 8:44 ` Xiao Ni
2022-11-16 17:11 ` Logan Gunthorpe
2022-11-03 8:14 ` Kinga Tanska
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=yq1tu3rtio1.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=David.Sloan@eideticom.com \
--cc=Martin.Oliveira@eideticom.com \
--cc=chaitanyak@nvidia.com \
--cc=colyli@suse.de \
--cc=guoqing.jiang@linux.dev \
--cc=jes@trained-monkey.org \
--cc=jm@chia.net \
--cc=linux-raid@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=sbates@raithlin.com \
--cc=xni@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.