From: Paul Wise <pabs3@bonedaddy.net>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] dm raid/raid1: enable discard support when any devices support discard
Date: Sat, 25 Apr 2020 10:46:40 +0800 [thread overview]
Message-ID: <92911928f258ce7d1649b138e71abff90cdf660d.camel@bonedaddy.net> (raw)
In-Reply-To: <20200419131908.GA22398@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Sun, 2020-04-19 at 09:19 -0400, Mike Snitzer wrote:
> You went overboard with implementation before checking to see if your
> work would be well received.
...
> I haven't looked closely at MD raid in this area but if you trully think
> underlying MD raid can cope with issuing discards to devices that don't
> support them (or that it avoids issuing them?) then please update
> dm-raid.c to conditionally set ti->discard_supported (if not all devices
> support discard). That is how to inform DM core that the target knows
> better and it will manage discards issued to it. It keeps the change
> local to dm-raid.c without the flag-day you're proposing.
So, now that I know that my approach to this was completely bogus,
what *is* the correct way to safely enable mixed-discard support?
It seems to me that the right way would be one of these options:
* a sysfs toggle for the block layer
* an lvchange based option for the dm layer
I'm leaning towards the latter for my personal use-case but the former
would make Linux much more flexible but would touch more code and have
the potential for more damage.
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-04-25 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 7:30 Paul Wise
2020-04-19 7:30 ` [PATCH 1/3] dm: add support for targets that allow discard when one device does Paul Wise
2020-04-19 7:30 ` [PATCH 2/3] dm raid: only check for RAID 4/5/6 once during discard support setup Paul Wise
2020-04-19 7:30 ` [PATCH 3/3] dm raid/raid1: enable discard support when any devices support discard Paul Wise
2020-04-19 13:19 ` [PATCH 0/3] " Mike Snitzer
2020-04-19 14:48 ` Paul Wise
2020-04-20 7:35 ` [dm-devel] " Ondrej Kozina
2020-04-20 10:13 ` Paul Wise
2020-04-20 10:22 ` Ondrej Kozina
2020-04-25 2:46 ` Paul Wise [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=92911928f258ce7d1649b138e71abff90cdf660d.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®