From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 13 Jul 2017 22:09:32 +0800 From: weiping zhang To: Jens Axboe CC: Subject: Re: [PATCH] blk-mq-debugfs: add mapping show for hw queue to cpu Message-ID: <20170713140932.GA18971@bogon.didichuxing.com> References: <20170712165400.GA9696@localhost.didichuxing.com> <20170712171331.GA13374@localhost.didichuxing.com> <3d69dcde-2f8e-b7e3-5a3a-f0cb7f8caee8@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: <3d69dcde-2f8e-b7e3-5a3a-f0cb7f8caee8@kernel.dk> Return-Path: zhangweiping@didichuxing.com List-ID: On Wed, Jul 12, 2017 at 11:25:12AM -0600, Jens Axboe wrote: > On 07/12/2017 11:13 AM, weiping zhang wrote: > > On Wed, Jul 12, 2017 at 10:57:37AM -0600, Jens Axboe wrote: > >> On 07/12/2017 10:54 AM, weiping zhang wrote: > >>> A mapping show as following: > >>> > >>> hctx cpus > >>> hctx0 0 1 > >>> hctx1 2 > >>> hctx2 3 > >>> hctx3 4 5 > >> > >> We already have that information in the /sys/block//mq/X/cpu_list > >> > >> where X is the hardware queue number. Why do we need it in debugfs as > >> well, presented differently? > > > > this arribute give a more obviously showing, only by 1 "cat" command. > > /sys/bloc//mq/X/cpu_list not easy get mapping for all hctx by 1 > > command. > > also /sys/kernel/debug/block/xxx/hctxN/cpuX can export that info, but > > these two methods both not obviously. > > The point is the information is there, and I'm sure most people can > work out the shell logic to collect this info. I see zero benefit to > adding this to debugfs. > Hi Jens, It seems no other people wanna this patch, please skip it, thanks for your replay ^_^. -- weiping