From: patchwork-bot+netdevbpf@kernel.org
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sundeep.lkml@gmail.com, hkelam@marvell.com, gakula@marvell.com,
sgoutham@marvell.com
Subject: Re: [v2 net-next PATCH 0/2] Add ethtool support for completion queue event size
Date: Thu, 24 Feb 2022 05:20:10 +0000 [thread overview]
Message-ID: <164568001003.3592.15842373523179006720.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1645555153-4932-1-git-send-email-sbhatta@marvell.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Feb 2022 00:09:11 +0530 you wrote:
> After a packet is sent or received by NIC then NIC posts
> a completion queue event which consists of transmission status
> (like send success or error) and received status(like
> pointers to packet fragments). These completion events may
> also use a ring similar to rx and tx rings. This patchset
> introduces cqe-size ethtool parameter to modify the size
> of the completion queue event if NIC hardware has that capability.
> A bigger completion queue event can have more receive buffer pointers
> inturn NIC can transfer a bigger frame from wire as long as
> hardware(MAC) receive frame size limit is not exceeded.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] ethtool: add support to set/get completion queue event size
https://git.kernel.org/netdev/net-next/c/1241e329ce2e
- [v2,net-next,2/2] octeontx2-pf: Vary completion queue event size
https://git.kernel.org/netdev/net-next/c/68258596cbc9
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-02-24 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 18:39 [v2 net-next PATCH 0/2] Add ethtool support for completion queue event size Subbaraya Sundeep
2022-02-22 18:39 ` [v2 net-next PATCH 1/2] ethtool: add support to set/get " Subbaraya Sundeep
2022-02-22 18:39 ` [v2 net-next PATCH 2/2] octeontx2-pf: Vary " Subbaraya Sundeep
2022-02-24 5:20 ` patchwork-bot+netdevbpf [this message]
2022-10-24 13:39 ` [v2 net-next PATCH 0/2] Add ethtool support for " Gal Pressman
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=164568001003.3592.15842373523179006720.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sundeep.lkml@gmail.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).