From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: dm-devel@redhat.com, linux-bcache@vger.kernel.org,
linux-block@vger.kernel.org
Subject: avoid the ->make_request_fn indirect for blk-mq drivers
Date: Sat, 25 Apr 2020 09:53:33 +0200 [thread overview]
Message-ID: <20200425075336.721021-1-hch@lst.de> (raw)
Hi Jens,
this small series avoids an indirect call for every submitted bio that
eventually ends up being handled by blk-mq drivers. Let me know what
you think.
next reply other threads:[~2020-04-25 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 7:53 Christoph Hellwig [this message]
2020-04-25 7:53 ` [PATCH 1/3] bcache: remove a duplicate ->make_request_fn assignment Christoph Hellwig
2020-04-25 7:53 ` Christoph Hellwig
2020-04-26 9:35 ` Coly Li
2020-04-25 7:53 ` [PATCH 2/3] dm: remove the make_request_fn check in device_area_is_invalid Christoph Hellwig
2020-04-25 7:53 ` Christoph Hellwig
2020-04-28 18:38 ` Mike Snitzer
2020-04-28 18:38 ` Mike Snitzer
2020-04-25 7:53 ` [PATCH 3/3] block: bypass ->make_request_fn for blk-mq drivers Christoph Hellwig
2020-04-25 7:53 ` Christoph Hellwig
2020-04-28 18:40 ` Mike Snitzer
2020-04-28 18:40 ` Mike Snitzer
2020-04-25 15:45 ` avoid the ->make_request_fn indirect " Jens Axboe
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=20200425075336.721021-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.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