LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Gwendal Grignou <gwendal@chromium.org>, evgreen@chromium.org
Cc: axboe@kernel.dk, asavery@chromium.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] loop: Better discard for block devices
Date: Fri, 02 Nov 2018 09:02:12 -0700 [thread overview]
Message-ID: <1541174532.196084.146.camel@acm.org> (raw)
In-Reply-To: <CAPUE2uuhfk7kstwO2kp_Rs=9QQPgGQGY+QqR76zpZpTkKp5Mig@mail.gmail.com>
On Thu, 2018-11-01 at 15:44 -0700, Gwendal Grignou wrote:
> On Thu, Nov 1, 2018 at 11:15 AM Evan Green <evgreen@chromium.org> wrote:
> >
> > On Tue, Oct 30, 2018 at 4:50 PM Bart Van Assche <bvanassche@acm.org> wrote:
> > >
> > > On Tue, 2018-10-30 at 16:06 -0700, Evan Green wrote:
> > > > This series addresses some errors seen when using the loop
> > > > device directly backed by a block device. The first change plumbs
> > > > out the correct error message, and the second change prevents the
> > > > error from occurring in many cases.
> > >
> > > Hi Evan,
> > >
> > > Can you provide some information about the use case? Why do you think that
> > > it would be useful to support backing a loop device by a block device? Why
> > > to use the loop driver instead of dm-linear for this use case?
> > >
> >
> > Hi Bart,
> > In our case, the Chrome OS installer uses the loop device to map
> > slices of the disk that will ultimately represent partitions [1]. I
> > believe it has been doing install this way for a very long time, and
> > has been working well. It actually continues to work, but on block
> > devices that don't support discard operations, things are a tiny bit
> > bumpy. This series is meant to smooth out those bumps. As far as I
> > knew this was a supported scenario.
> >
> > -Evan
> > [1] https://chromium.googlesource.com/chromiumos/platform/installer/+/master/chromeos-install
>
> The code has moved to
> https://chromium.googlesource.com/chromiumos/platform2/+/master/installer/chromeos-install
> but the idea is the same. We create a loop device to abstract the
> persistent destination. The destination can be a block device or a
> file. The later case is used for creating master images to be flashed
> on memory chip before soldering on the production line.
> It is handy when the final device is 4K block aligned but the builder
> is using 512b block aligned device, we can mount a device over a file
> that will behave like the real device we will flash the image on.
Hi Evan and Gwendal,
Since this is a new use case for the loop driver you may want to add a test
for this use case to the blktests project. Many block layer contributors run
these tests to verify their own block layer changes. Contributing a blktests
test for this new use case will make it easier for others to verify that
their changes do not break your use case.
Bart.
next prev parent reply other threads:[~2018-11-02 16:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 23:06 Evan Green
2018-10-30 23:06 ` [PATCH 1/2] loop: Report EOPNOTSUPP properly Evan Green
2018-11-28 1:06 ` Ming Lei
2018-10-30 23:06 ` [PATCH 2/2] loop: Better discard support for block devices Evan Green
2018-11-26 18:53 ` Evan Green
2018-11-27 2:55 ` Ming Lei
2018-11-27 23:34 ` Evan Green
2018-11-28 1:28 ` Ming Lei
2018-11-28 1:26 ` Ming Lei
2018-12-04 22:19 ` Evan Green
2018-12-05 1:10 ` Ming Lei
2018-12-05 19:35 ` Evan Green
2018-12-06 0:22 ` Ming Lei
2018-12-06 3:15 ` Martin K. Petersen
2018-12-10 17:31 ` Evan Green
2018-12-18 23:48 ` Evan Green
2018-10-30 23:50 ` [PATCH 0/2] loop: Better discard " Bart Van Assche
2018-11-01 18:15 ` Evan Green
2018-11-01 22:44 ` Gwendal Grignou
2018-11-02 16:02 ` Bart Van Assche [this message]
2018-11-05 20:35 ` Evan Green
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=1541174532.196084.146.camel@acm.org \
--to=bvanassche@acm.org \
--cc=asavery@chromium.org \
--cc=axboe@kernel.dk \
--cc=evgreen@chromium.org \
--cc=gwendal@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH 0/2] loop: Better discard for block devices' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).