linux-kernel - blk-mq : blk_mq_map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <806c215d-fd17-471d-96a7-9c083b9fe7db@aliyun.com>
Date:	Wed, 08 Apr 2015 10:10:27 +0800
From:	"nimisolo" <nimisolo@...yun.com>
To:	"axboe" <axboe@...nel.dk>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: blk-mq : blk_mq_map_swqueue maybe

Hi Jens,

In blk_mq_map_swqueue(), all the blk_mq_hw_ctx's  nr_ctx  are set  
to zero, and then each blk_mq_ctx's  index_hw  is set to nr_ctx. 
I think the index_hw means the index of the hardware queue that map 
to this software queue, so maybe index_hw should be set to 
blk_mq_hw_ctx's queue_num.

I'm a student and I probably have misunderstood this code, please help
me to resolve this confusion. Thank you.

static void blk_mq_map_swqueue(struct request_queue *q)
{
        .........
        queue_for_each_hw_ctx(q, hctx, i) {
                .........
                hctx->nr_ctx = 0;
        }
        .........
        queue_for_each_ctx(q, ctx, i) {
                .........
                ctx->index_hw = hctx->nr_ctx;
                .........
        }
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/