From: Jakub Kicinski <kuba@kernel.org>
To: "mengyuanlou@net-swift.com" <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
duanqiangwen@net-swift.com
Subject: Re: [PATCH net-next v7 5/6] net: ngbe: add sriov function support
Date: Wed, 12 Feb 2025 18:09:12 -0800 [thread overview]
Message-ID: <20250212180912.7dc3e3cf@kernel.org> (raw)
In-Reply-To: <DF81ED4C-F36A-4D6C-8993-0389E2F39615@net-swift.com>
On Wed, 12 Feb 2025 19:06:52 +0800 mengyuanlou@net-swift.com wrote:
> > The goal should be to make sure the right handler is register
> > for the IRQ, or at least do the muxing earlier in a safe fashion.
> > Not decide that it was a packet IRQ half way thru a function called
> > ngbe_msix_other
>
> Whether the first way(Alloc 9 irq vectors, but only request_irq for 0
> and 8) can be better than reuse vector 0 in the real?
I don't understand, sorry.
next prev parent reply other threads:[~2025-02-13 2:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 10:37 [PATCH net-next v7 0/6] add sriov support for wangxun NICs mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 1/6] net: libwx: Add malibox api for wangxun pf drivers mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 2/6] net: libwx: Add sriov api for wangxun nics mengyuanlou
2025-02-08 1:12 ` Jakub Kicinski
2025-02-06 10:37 ` [PATCH net-next v7 3/6] net: libwx: Redesign flow when sriov is enabled mengyuanlou
2025-02-08 1:15 ` Jakub Kicinski
2025-02-11 11:17 ` mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 4/6] net: libwx: Add msg task func mengyuanlou
2025-02-08 1:17 ` Jakub Kicinski
2025-02-11 11:14 ` mengyuanlou
2025-02-06 10:37 ` [PATCH net-next v7 5/6] net: ngbe: add sriov function support mengyuanlou
2025-02-08 1:19 ` Jakub Kicinski
2025-02-11 11:14 ` mengyuanlou
2025-02-11 22:06 ` Jakub Kicinski
2025-02-12 11:06 ` mengyuanlou
2025-02-13 2:09 ` Jakub Kicinski [this message]
2025-02-06 10:37 ` [PATCH net-next v7 6/6] net: txgbe: " mengyuanlou
2025-02-08 1:09 ` 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=20250212180912.7dc3e3cf@kernel.org \
--to=kuba@kernel.org \
--cc=duanqiangwen@net-swift.com \
--cc=jiawenwu@trustnetic.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.