From: Jason Gunthorpe <jgg@ziepe.ca>
To: Wei Hu <weh@microsoft.com>
Cc: netdev@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-rdma@vger.kernel.org, longli@microsoft.com,
sharmaajay@microsoft.com, leon@kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, vkuznets@redhat.com,
ssengar@linux.microsoft.com, shradhagupta@linux.microsoft.com
Subject: Re: [PATCH v4 1/1] RDMA/mana_ib: Add EQ interrupt support to mana ib driver.
Date: Fri, 28 Jul 2023 14:43:12 -0300 [thread overview]
Message-ID: <ZMP+MH7f/Vk9/J0b@ziepe.ca> (raw)
In-Reply-To: <20230728170749.1888588-1-weh@microsoft.com>
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
next prev parent reply other threads:[~2023-07-28 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:07 [PATCH v4 1/1] RDMA/mana_ib: Add EQ interrupt support to mana ib driver Wei Hu
2023-07-28 17:43 ` Jason Gunthorpe [this message]
2023-07-28 17:51 ` Long Li
2023-07-28 18:02 ` Jason Gunthorpe
2023-07-28 18:22 ` Long Li
2023-07-28 18:39 ` Jason Gunthorpe
2023-08-01 19:06 ` Long Li
2023-08-01 23:46 ` Jason Gunthorpe
2023-08-02 4:11 ` [EXTERNAL] " Ajay Sharma
2023-08-02 13:08 ` Jason Gunthorpe
2023-08-15 22:51 ` Long Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZMP+MH7f/Vk9/J0b@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmaajay@microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=vkuznets@redhat.com \
--cc=weh@microsoft.com \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox