[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZMP+MH7f/Vk9/J0b@ziepe.ca>
Date: Fri, 28 Jul 2023 14:43:12 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Wei Hu <weh@...rosoft.com>
Cc: netdev@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-rdma@...r.kernel.org, longli@...rosoft.com,
sharmaajay@...rosoft.com, leon@...nel.org, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, vkuznets@...hat.com, ssengar@...ux.microsoft.com,
shradhagupta@...ux.microsoft.com
Subject: Re: [PATCH v4 1/1] RDMA/mana_ib: Add EQ interrupt support to mana ib
driver.
On Fri, Jul 28, 2023 at 05:07:49PM +0000, Wei Hu wrote:
> Add EQ interrupt support for mana ib driver. Allocate EQs per ucontext
> to receive interrupt. Attach EQ when CQ is created. Call CQ interrupt
> handler when completion interrupt happens. EQs are destroyed when
> ucontext is deallocated.
It seems strange that interrupts would be somehow linked to a
ucontext? interrupts are highly limited, you can DOS the entire system
if someone abuses this.
Generally I expect a properly functioning driver to use one interrupt
per CPU core.
You should tie the CQ to a shared EQ belong to the core that the CQ
wants to have affinity to.
Jason
Powered by blists - more mailing lists