From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: BLK_MQ_F_DEFER_ISSUE
Date: Mon, 20 Apr 2015 09:58:48 -0600 [thread overview]
Message-ID: <55352238.1020301@kernel.dk> (raw)
In-Reply-To: <x49twwa7s6m.fsf@segfault.boston.devel.redhat.com>
On 04/20/2015 09:09 AM, Jeff Moyer wrote:
> Hi, Jens,
>
> This flag was introduced under the auspices that the nvme blk-mq
> conversion would make use of it. That never materialized. Are there
> still plans to make use of it? If not, I'd like to get rid of it. If
> so, then let's document it better.
Yep I still want to use it, and I do have a patch that uses it as well
that I've run through testing. I thought I had pushed it somewhere, but
it doesn't seem like I have. I just wanted to get the lower hanging
optimizations out there first, like the kmalloc/kfree and
queue-lock-for-completions removal. Former is in, latter is not yet.
It's a useful optimization for lots of cases and I'm sure it'll see
other uses, once the nvme patch is in. That will give people a reference
point.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-20 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 15:09 BLK_MQ_F_DEFER_ISSUE Jeff Moyer
2015-04-20 15:58 ` Jens Axboe [this message]
2015-04-20 16:04 ` BLK_MQ_F_DEFER_ISSUE Jeff Moyer
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=55352238.1020301@kernel.dk \
--to=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@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