[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8f375d7-8a1f-39f5-5fd6-0bdc781f1465@grimberg.me>
Date: Mon, 16 Jul 2018 17:59:05 +0300
From: Sagi Grimberg <sagi@...mberg.me>
To: Max Gurtovoy <maxg@...lanox.com>, Leon Romanovsky <leon@...nel.org>
Cc: Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
RDMA mailing list <linux-rdma@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>,
Steve Wise <swise@...ngridcomputing.com>,
linux-netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH mlx5-next] RDMA/mlx5: Don't use cached IRQ affinity mask
> Hi,
> I've tested this patch and seems problematic at this moment.
Problematic how? what are you seeing?
> maybe this is because of the bug that Steve mentioned in the NVMe
> mailing list. Sagi mentioned that we should fix it in the NVMe/RDMA
> initiator and I'll run his suggestion as well.
Is your device irq affinity linear?
> BTW, when I run the blk_mq_map_queues it works for every irq affinity.
But its probably not aligned to the device vector affinity.
Powered by blists - more mailing lists