From: Christoph Hellwig <hch@lst.de>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
Jens Axboe <axboe@kernel.dk>,
Dan Schatzberg <schatzberg.dan@gmail.com>,
kernel test robot <oliver.sang@intel.com>,
Jan Stancek <jstancek@redhat.com>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] loop: use task_work for autoclear operation
Date: Tue, 18 Jan 2022 17:15:26 +0100 [thread overview]
Message-ID: <20220118161526.GA30337@lst.de> (raw)
In-Reply-To: <f6b947d0-1047-66b3-0243-af5017c9ab55@I-love.SAKURA.ne.jp>
I'll try to take a look. I've been busy today coming up with a scheme
that avoids taking ->open_mutex outside the open/release path at all,
which should also help, but it's not quite ready.
next prev parent reply other threads:[~2022-01-18 16:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 11:00 [PATCH v2 1/2] block: export task_work_add() Tetsuo Handa
2022-01-07 11:04 ` [PATCH v2 2/2] loop: use task_work for autoclear operation Tetsuo Handa
2022-01-10 6:20 ` Jan Stancek
2022-01-10 10:30 ` Jan Kara
2022-01-10 11:28 ` Tetsuo Handa
2022-01-10 13:42 ` Jan Kara
2022-01-10 15:08 ` Tetsuo Handa
2022-01-12 13:16 ` Jan Kara
2022-01-12 14:00 ` Tetsuo Handa
2022-01-13 15:23 ` Jan Kara
2022-01-14 11:05 ` Tetsuo Handa
2022-01-14 16:05 ` Jan Kara
2022-01-13 10:44 ` Jan Kara
2022-01-14 15:50 ` Tetsuo Handa
2022-01-14 19:58 ` Jan Kara
2022-01-15 0:34 ` Tetsuo Handa
2022-01-17 8:15 ` Christoph Hellwig
2022-01-17 9:34 ` Tetsuo Handa
2022-01-17 14:10 ` Tetsuo Handa
2022-01-18 15:58 ` Tetsuo Handa
2022-01-18 16:15 ` Christoph Hellwig [this message]
2022-01-20 14:20 ` Christoph Hellwig
2022-01-20 15:42 ` Jan Kara
2022-01-10 16:40 ` Christoph Hellwig
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=20220118161526.GA30337@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=jstancek@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=schatzberg.dan@gmail.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.