From: Andrew Lunn <andrew@lunn.ch>
To: han.junyang@zte.com.cn
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
ran.ming@zte.com.cn, han.chengfei@zte.com.cn,
zhang.yanze@zte.com.cn
Subject: Re: [PATCH net-next v1 2/3] dinghai: add MSI-X interrupt pools
Date: Tue, 25 Aug 2026 01:55:44 +0200 [thread overview]
Message-ID: <ac2a9538-8464-461d-b320-e7f295f4b28c@lunn.ch> (raw)
In-Reply-To: <20260824033752114y7ecQBMlUK_K6MxQNt7gu@zte.com.cn>
> + * Device vectors are managed in per-purpose pools. An IRQ carries a
> + * refcount so that several event queues can share one vector; on
> + * raise, the interrupt is fanned out through an atomic notifier chain
> + * attached to the IRQ.
> +static int zxdh_irq_get_locked(struct zxdh_irq *irq)
> +{
> + lockdep_assert_held(&irq->pool->lock);
> + if (WARN_ON_ONCE(!irq->refcount))
> + return 0;
> +
> + irq->refcount++;
Why not use kref?
Andrew
next prev parent reply other threads:[~2026-08-24 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 19:32 [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue han.junyang
2026-08-23 19:35 ` [PATCH net-next v1 1/3] dinghai: add firmware version check and RISC-V readiness polling han.junyang
2026-08-23 21:55 ` [PATCH net-next v1 1/3] dinghai: add firmware version check and? " Andrew Lunn
2026-08-24 17:59 ` Andrew Lunn
2026-08-23 19:37 ` [PATCH net-next v1 2/3] dinghai: add MSI-X interrupt pools han.junyang
2026-08-24 23:55 ` Andrew Lunn [this message]
2026-08-23 19:40 ` [PATCH net-next v1 3/3] dinghai: add async event queue for firmware notifications han.junyang
2026-08-24 17:00 ` [PATCH net-next v1 0/3] dinghai: firmware handshake, MSI-X interrupts and async event queue Jakub Kicinski
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=ac2a9538-8464-461d-b320-e7f295f4b28c@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=han.chengfei@zte.com.cn \
--cc=han.junyang@zte.com.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ran.ming@zte.com.cn \
--cc=zhang.yanze@zte.com.cn \
/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
all inboxes | Powered by JetHome®