From: Martijn Coenen <maco@android.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
kernel-team@android.com, Narayan Kamath <narayan@google.com>,
Dario Freni <dariofreni@google.com>,
Nikita Ioffe <ioffe@google.com>, Jiyong Park <jiyong@google.com>,
Martijn Coenen <maco@google.com>
Subject: Re: [PATCH] RFC: loop: Avoid calling blk_mq_freeze_queue() when possible.
Date: Thu, 15 Aug 2019 15:49:58 +0100 [thread overview]
Message-ID: <CAB0TPYGczqoDz=ReM75cYc4hbS58V-a4m_qJ8GoAoWtepXTWNA@mail.gmail.com> (raw)
In-Reply-To: <29990045-b05e-1411-a5c2-32e735265a04@acm.org>
On Wed, Aug 14, 2019 at 4:29 PM Bart Van Assche <bvanassche@acm.org> wrote:
> Hi Martijn,
>
> Is the loop driver used in Android Q to make a file on a filesystem
> visible as a block device or rather to make a subset of a block device
> visible as a block device? In the latter case, have you considered to
> use the dm-linear driver instead? I expect that the overhead per I/O of
> dm-linear will be lower than that of the loop driver.
Hi Bart,
In this case we're using the loop driver to make a file on the
filesystem visible as a block device (in the file is a filesystem we
want to mount), so unfortunately dm-linear is not an option.
Best,
Martijn
>
> Bart.
prev parent reply other threads:[~2019-08-15 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:32 [PATCH] RFC: loop: Avoid calling blk_mq_freeze_queue() when possible Martijn Coenen
2019-08-14 11:33 ` Ming Lei
2019-08-14 11:38 ` Martijn Coenen
2019-08-14 11:46 ` Ming Lei
2019-08-15 14:57 ` Martijn Coenen
2019-08-15 16:34 ` Ming Lei
2019-08-15 19:08 ` Martijn Coenen
2019-08-19 9:06 ` Martijn Coenen
2019-08-19 9:26 ` Martijn Coenen
2019-08-14 15:29 ` Bart Van Assche
2019-08-15 14:49 ` Martijn Coenen [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='CAB0TPYGczqoDz=ReM75cYc4hbS58V-a4m_qJ8GoAoWtepXTWNA@mail.gmail.com' \
--to=maco@android.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dariofreni@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ioffe@google.com \
--cc=jiyong@google.com \
--cc=kernel-team@android.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@google.com \
--cc=narayan@google.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;
as well as URLs for NNTP newsgroup(s).