From: patchwork-bot+netdevbpf@kernel.org
To: Shinas Rasheed <srasheed@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hgani@marvell.com, vimleshk@marvell.com, egallen@redhat.com,
mschmidt@redhat.com, pabeni@redhat.com, horms@kernel.org,
kuba@kernel.org, davem@davemloft.net, wizhao@redhat.com,
konguyen@redhat.com
Subject: Re: [PATCH net-next v3 RESEND 0/4] Cleanup and optimizations to transmit code
Date: Thu, 16 Nov 2023 22:00:23 +0000 [thread overview]
Message-ID: <170017202386.32455.7477139166082285049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231114134535.2455051-1-srasheed@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 14 Nov 2023 05:45:31 -0800 you wrote:
> Pad small packets to ETH_ZLEN before transmit, cleanup dma sync calls,
> add xmit_more functionality and then further remove atomic
> variable usage in the prior.
>
> Changes:
> V3:
> - Stop returning NETDEV_TX_BUSY when ring is full in xmit_patch.
> Change to inspect early if next packet can fit in ring instead of
> current packet, and stop queue if not.
> - Add smp_mb between stopping tx queue and checking if tx queue has
> free entries again, in queue full check function to let reflect
> IQ process completions that might have happened on other cpus.
> - Update small packet padding patch changelog to give more info.
> V2: https://lore.kernel.org/all/20231024145119.2366588-1-srasheed@marvell.com/
> - Added patch for padding small packets to ETH_ZLEN, part of
> optimization patches for transmit code missed out in V1
> - Updated changelog to provide more details for dma_sync remove patch
> - Updated changelog to use imperative tone in add xmit_more patch
> V1: https://lore.kernel.org/all/20231023114449.2362147-1-srasheed@marvell.com/
>
> [...]
Here is the summary with links:
- [net-next,v3,RESEND,1/4] octeon_ep: add padding for small packets
https://git.kernel.org/netdev/net-next/c/5827fe2bc9c4
- [net-next,v3,RESEND,2/4] octeon_ep: remove dma sync in trasmit path
https://git.kernel.org/netdev/net-next/c/2fba5069959c
- [net-next,v3,RESEND,3/4] octeon_ep: implement xmit_more in transmit
https://git.kernel.org/netdev/net-next/c/373d9a55ba74
- [net-next,v3,RESEND,4/4] octeon_ep: remove atomic variable usage in Tx data path
https://git.kernel.org/netdev/net-next/c/dc9c02b7faa0
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-11-16 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 13:45 [PATCH net-next v3 RESEND 0/4] Cleanup and optimizations to transmit code Shinas Rasheed
2023-11-14 13:45 ` [PATCH net-next v3 RESEND 1/4] octeon_ep: add padding for small packets Shinas Rasheed
2023-11-14 13:45 ` [PATCH net-next v3 RESEND 2/4] octeon_ep: remove dma sync in trasmit path Shinas Rasheed
2023-11-14 13:45 ` [PATCH net-next v3 RESEND 3/4] octeon_ep: implement xmit_more in transmit Shinas Rasheed
2023-11-14 13:45 ` [PATCH net-next v3 RESEND 4/4] octeon_ep: remove atomic variable usage in Tx data path Shinas Rasheed
2023-11-16 22:00 ` 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=170017202386.32455.7477139166082285049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srasheed@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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).