On Fri, Sep 19, 2014 at 11:21 PM, Bart Van Assche <bvanassche@xxxxxxx> wrote:
> On 09/19/14 16:28, Ming Lei wrote:
>>
>> On Fri, Sep 19, 2014 at 9:00 PM, Bart Van Assche <bvanassche@xxxxxxx>
>> wrote:
>>>
>>> @@ -2643,7 +2754,8 @@ static struct scsi_host_template srp_template = {
>>> .proc_name = DRV_NAME,
>>> .slave_configure = srp_slave_configure,
>>> .info = srp_target_info,
>>> - .queuecommand = srp_queuecommand,
>>> + .queuecommand = srp_sq_queuecommand,
>>> + .mq_queuecommand = srp_mq_queuecommand,
>>
>>
>> Another choice is to obtain hctx from request directly, then mq can
>> reuse the .queuecommand interface too.
>
>
> Hello Ming,
>
> Is the hctx information already available in the request data structure ? I
> have found a mq_ctx member but no hctx member. Did I perhaps overlook
> something ?
You are right, but the mq_ctx can be mapped to hctx like below way:
ctx = rq->mq_ctx;
hctx = q->mq_ops->map_queue(q, ctx->cpu);
Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
