Re: [PATCH 0/3] blk-mq & nvme: introduce .map_changed
From: Ming Lei
Date: Tue Sep 29 2015 - 17:59:54 EST
On Tue, Sep 29, 2015 at 3:07 PM, Christoph Hellwig <hch@xxxxxx> wrote:
> 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.
The mapped parameter can be removed since it can be figured out by
IMO, it isn't good to split it into two callback, such as,
map_activate/map_deactivate or other names, and the two callback
can't be symmetrical at all. When CPU hotplug happened, it is just
the mapping changed, neigher setuping nor tearing down since it is
1:N mapping between hw queue and percpu sw queue.
So I suggest to keep it as .map_changed(), or do you have better idea?
> Please keep Akinobu Mita in the loop, as this should go on top of his blk-mq
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/