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
> >>> hc
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:
>>>
>>> hctxcpus
>>> hctx0 0 1
>>> hctx1 2
>>> hctx2
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:
> >
> > hctxcpus
> > hctx0 0 1
> > hctx1 2
> > hctx2 3
> > hctx3 4 5
>
>
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 d
A mapping show as following:
hctxcpus
hctx0 0 1
hctx1 2
hctx2 3
hctx3 4 5
Signed-off-by: weiping zhang
---
block/blk-mq-debugfs.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/block/blk-mq-debugfs.c b/bloc