From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
Mike Snitzer <snitzer@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
dm-devel@redhat.com, tj@kernel.org,
Dennis Zhou <dennis@kernel.org>
Subject: Re: [dm-devel] can we reduce bio_set_dev overhead due to bio_associate_blkg?
Date: Fri, 8 Apr 2022 22:15:41 -0700 [thread overview]
Message-ID: <YlEWfc39+H+esrQm@infradead.org> (raw)
In-Reply-To: <YlBX+ytxxeSj2neQ@redhat.com>
On Fri, Apr 08, 2022 at 11:42:51AM -0400, Mike Snitzer wrote:
> I think we can achieve the goal of efficient cloning/remapping for
> both usecases simply by splitting out the bio_set_dev() and leaving it
> to the caller to pick which interface to use (e.g. clone vs
> clone_and_remap).
You can just pass a NULL bdev to bio_alloc_clone/bio_init_clone.
I've been hoping to get rid of that, but if we have a clear use case
it will have to stay.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2022-04-09 5:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:52 [dm-devel] can we reduce bio_set_dev overhead due to bio_associate_blkg? Mike Snitzer
2022-03-30 12:28 ` Dennis Zhou
2022-03-31 4:39 ` Christoph Hellwig
2022-03-31 5:52 ` Dennis Zhou
2022-03-31 9:15 ` Christoph Hellwig
2022-04-08 15:42 ` Mike Snitzer
2022-04-09 5:15 ` Christoph Hellwig [this message]
2022-04-11 16:58 ` Mike Snitzer
2022-04-11 17:16 ` Mike Snitzer
2022-04-11 17:33 ` [dm-devel] [PATCH] block: remove redundant blk-cgroup init from __bio_clone Mike Snitzer
2022-04-12 5:27 ` Christoph Hellwig
2022-04-12 7:52 ` Dennis Zhou
2022-04-23 16:55 ` Christoph Hellwig
2022-04-26 17:30 ` [dm-devel] " Mike Snitzer
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=YlEWfc39+H+esrQm@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dennis@kernel.org \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=snitzer@redhat.com \
--cc=tj@kernel.org \
/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