From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Tyler Hicks <tyhicks@linux.microsoft.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>, James Morris <jmorris@namei.org>,
lukas.bulwahn@gmail.com, hch@lst.de, ming.lei@redhat.com,
mzxreary@0pointer.de, mcgrof@kernel.org, zhengbin13@huawei.com,
maco@android.com, Colin King <colin.king@canonical.com>,
evgreen@chromium.org
Subject: Re: [PATCH v3 1/1] loop: scale loop device by introducing per device lock
Date: Tue, 26 Jan 2021 09:22:48 -0500 [thread overview]
Message-ID: <CA+CK2bBVdVOP6TmJED4Wndovxf+dGbcbw=0LQ8neAGL_2=TEwA@mail.gmail.com> (raw)
In-Reply-To: <YA/fwFU+Wg6+jr85@pevik>
On Tue, Jan 26, 2021 at 4:24 AM Petr Vorel <pvorel@suse.cz> wrote:
>
> Hi,
>
> > Currently, loop device has only one global lock:
> > loop_ctl_mutex.
>
> > This becomes hot in scenarios where many loop devices are used.
>
> > Scale it by introducing per-device lock: lo_mutex that protects the
> > fields in struct loop_device. Keep loop_ctl_mutex to protect global
> > data such as loop_index_idr, loop_lookup, loop_add.
>
> > Lock ordering: loop_ctl_mutex > lo_mutex.
>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
Thank you for reviewing this patch.
Pasha
next prev parent reply other threads:[~2021-01-26 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 20:11 [PATCH v3 0/1] scale loop device lock Pavel Tatashin
2021-01-25 20:11 ` [PATCH v3 1/1] loop: scale loop device by introducing per " Pavel Tatashin
2021-01-26 9:24 ` Petr Vorel
2021-01-26 14:22 ` Pavel Tatashin [this message]
2021-01-26 9:53 ` Chaitanya Kulkarni
2021-01-26 14:29 ` Pavel Tatashin
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='CA+CK2bBVdVOP6TmJED4Wndovxf+dGbcbw=0LQ8neAGL_2=TEwA@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=axboe@kernel.dk \
--cc=colin.king@canonical.com \
--cc=evgreen@chromium.org \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=maco@android.com \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=mzxreary@0pointer.de \
--cc=pvorel@suse.cz \
--cc=sashal@kernel.org \
--cc=tyhicks@linux.microsoft.com \
--cc=zhengbin13@huawei.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.