From: patchwork-bot+netdevbpf@kernel.org
To: Konstantin Taranov <kotaranov@linux.microsoft.com>
Cc: kotaranov@microsoft.com, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, kuba@kernel.org,
leon@kernel.org, decui@microsoft.com, edumazet@google.com,
cai.huoqing@linux.dev, pabeni@redhat.com, davem@davemloft.net,
longli@microsoft.com, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2] net: mana: add msix index sharing between EQs
Date: Fri, 15 Dec 2023 10:30:24 +0000 [thread overview]
Message-ID: <170263622459.29656.3858446025399076996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1702461707-2692-1-git-send-email-kotaranov@linux.microsoft.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 13 Dec 2023 02:01:47 -0800 you wrote:
> From: Konstantin Taranov <kotaranov@microsoft.com>
>
> This patch allows to assign and poll more than one EQ on the same
> msix index.
> It is achieved by introducing a list of attached EQs in each IRQ context.
> It also removes the existing msix_index map that tried to ensure that there
> is only one EQ at each msix_index.
> This patch exports symbols for creating EQs from other MANA kernel modules.
>
> [...]
Here is the summary with links:
- [for-next,v2] net: mana: add msix index sharing between EQs
https://git.kernel.org/netdev/net-next/c/02fed6d92bad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-15 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:01 [PATCH for-next v2] net: mana: add msix index sharing between EQs Konstantin Taranov
2023-12-15 10:30 ` patchwork-bot+netdevbpf [this message]
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=170263622459.29656.3858446025399076996.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=kotaranov@linux.microsoft.com \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).