From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Xiao Ni <xni@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: [RFC PATCH] mdadm: add --fast-initialize
Date: Mon, 10 Jun 2024 10:57:25 +0200 [thread overview]
Message-ID: <20240610105725.00002687@linux.intel.com> (raw)
In-Reply-To: <70ae9c73-ae48-4cc9-9118-e4e74102f090@deltatee.com>
On Tue, 4 Jun 2024 10:19:59 -0600
Logan Gunthorpe <logang@deltatee.com> wrote:
> On 2024-06-04 06:46, Xiao Ni wrote:
> > Hi Mariusz
> >
> > The discard can't promise to write zero to nvme disks, right? If so,
> > we can't use it for resync, because it can't make sure the raid is in
> > sync state.
>
> Yes, discard requests are a best effort and the drive is free to ignore
> some or all of the request. See [1] for more information from Martin
> Peterson.
>
> I think if we have a device that has a fast zero operation that we know
> guarantees zeroing then the kernel's write-zeros operation should be
> changed to use it. We shouldn't make fast-but-dangerous options in mdadm.
>
> Thanks,
>
> Logan
>
>
> [1] https://lore.kernel.org/all/yq1fsgwbijv.fsf@ca-mkp.ca.oracle.com/T/#u
Thanks for giving the valuable feedback. I'm not directly involved in technical
details about this implementation and in fact I didn't read the previous
discussion yet. You pointed great problem and I will make sure that it is
addressed.
I asked about mdadm API, it is despite the technical implementation.
I would like to propose one command to integrate existing way (--write-zeroes)
and potentially new way (if any other fast-initialization capability would be
safe to add).
Do you see it as right approach or we should keep them separately?
Mariusz
prev parent reply other threads:[~2024-06-10 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:33 [RFC PATCH] mdadm: add --fast-initialize Mariusz Tkaczyk
2024-06-04 12:46 ` Xiao Ni
2024-06-04 16:19 ` Logan Gunthorpe
2024-06-10 8:57 ` Mariusz Tkaczyk [this message]
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=20240610105725.00002687@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=logang@deltatee.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.