From: patchwork-bot+netdevbpf@kernel.org
To: Andrey Turkin <andrey.turkin@gmail.com>
Cc: netdev@vger.kernel.org, doshir@vmware.com, pv-drivers@vmware.com
Subject: Re: [PATCH] vmxnet3: Record queue number to incoming packets
Date: Tue, 19 Jul 2022 03:50:14 +0000 [thread overview]
Message-ID: <165820261432.2183.3392083130011514670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220717022050.822766-2-andrey.turkin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 17 Jul 2022 02:20:50 +0000 you wrote:
> Make generic XDP processing attribute packets to their actual
> queues instead of queue #0. This improves AF_XDP performance
> considerably since softirq threads no longer fight over single
> AF_XDP socket spinlock.
>
> Signed-off-by: Andrey Turkin <andrey.turkin@gmail.com>
>
> [...]
Here is the summary with links:
- vmxnet3: Record queue number to incoming packets
https://git.kernel.org/netdev/net-next/c/bdeed8b0958c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-19 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 2:20 [PATCH] vmxnet3: Implement ethtool's get_channels command Andrey Turkin
2022-07-17 2:20 ` [PATCH] vmxnet3: Record queue number to incoming packets Andrey Turkin
2022-07-19 3:50 ` patchwork-bot+netdevbpf [this message]
2022-07-17 3:37 ` [PATCH] vmxnet3: Implement ethtool's get_channels command kernel test robot
2022-07-17 5:22 ` kernel test robot
2022-07-17 14:54 ` Andrew Lunn
2022-07-17 16:03 ` kernel test robot
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=165820261432.2183.3392083130011514670.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrey.turkin@gmail.com \
--cc=doshir@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
/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 NNTP newsgroup(s).