From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 0/3] blk-mq & nvme: introduce .map_changed
Date: Tue, 29 Sep 2015 09:07:22 +0200 [thread overview]
Message-ID: <20150929070722.GA15110@lst.de> (raw)
In-Reply-To: <1443496857-26887-1-git-send-email-tom.leiming@gmail.com>
Hi Ming,
from a quick gance this looks very useful. Please split the callback
into two instead of overloading them with the bool mapped parameter.
Please keep Akinobu Mita in the loop, as this should go on top of his blk-mq
fixes.
next prev parent reply other threads:[~2015-09-29 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 3:20 [PATCH 0/3] blk-mq & nvme: introduce .map_changed Ming Lei
2015-09-29 3:20 ` [PATCH 1/3] blk-mq: introduce .map_changed to blk_mq_ops Ming Lei
2015-09-29 3:20 ` [PATCH 2/3] block: nvme: use map_changed to set irq affinity hint Ming Lei
2015-09-29 3:20 ` [PATCH 3/3] blk-mq: remove cpumask from 'struct blk_mq_tags' Ming Lei
2015-09-29 7:07 ` Christoph Hellwig [this message]
2015-09-29 21:59 ` [PATCH 0/3] blk-mq & nvme: introduce .map_changed Ming Lei
2015-09-29 14:26 ` Keith Busch
2015-09-29 14:47 ` Jens Axboe
2015-09-29 22:16 ` Ming Lei
2015-09-29 22:45 ` Keith Busch
2015-09-30 0:08 ` Ming Lei
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=20150929070722.GA15110@lst.de \
--to=hch@lst.de \
/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;
as well as URLs for NNTP newsgroup(s).