[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <92911928f258ce7d1649b138e71abff90cdf660d.camel@bonedaddy.net>
Date: Sat, 25 Apr 2020 10:46:40 +0800
From: Paul Wise <pabs3@...edaddy.net>
To: Mike Snitzer <snitzer@...hat.com>
Cc: Alasdair Kergon <agk@...hat.com>, dm-devel@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] dm raid/raid1: enable discard support when any
devices support discard
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/
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists