All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	po.liu@nxp.com, claudiu.manoil@nxp.com,
	alexandru.marginean@nxp.com, yangbo.lu@nxp.com, toke@redhat.com,
	vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next 00/10] Fixups for XDP on NXP ENETC
Date: Sat, 17 Apr 2021 00:20:13 +0000	[thread overview]
Message-ID: <161861881380.3813.7857023133457832186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210416212225.3576792-1-olteanv@gmail.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Sat, 17 Apr 2021 00:22:15 +0300 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> After some more XDP testing on the NXP LS1028A, this is a set of 10 bug
> fixes, simplifications and tweaks, ranging from addressing Toke's feedback
> (the network stack can run concurrently with XDP on the same TX rings)
> to fixing some OOM conditions seen under TX congestion.
> 
> [...]

Here is the summary with links:
  - [net-next,01/10] net: enetc: remove redundant clearing of skb/xdp_frame pointer in TX conf path
    https://git.kernel.org/netdev/net-next/c/e9e49ae88ec8
  - [net-next,02/10] net: enetc: rename the buffer reuse helpers
    https://git.kernel.org/netdev/net-next/c/6b04830d5e0d
  - [net-next,03/10] net: enetc: recycle buffers for frames with RX errors
    https://git.kernel.org/netdev/net-next/c/672f9a21989e
  - [net-next,04/10] net: enetc: stop XDP NAPI processing when build_skb() fails
    https://git.kernel.org/netdev/net-next/c/8f50d8bb3f1c
  - [net-next,05/10] net: enetc: remove unneeded xdp_do_flush_map()
    https://git.kernel.org/netdev/net-next/c/a6369fe6e07d
  - [net-next,06/10] net: enetc: increase TX ring size
    https://git.kernel.org/netdev/net-next/c/ee3e875f10fc
  - [net-next,07/10] net: enetc: use dedicated TX rings for XDP
    https://git.kernel.org/netdev/net-next/c/7eab503b11ee
  - [net-next,08/10] net: enetc: handle the invalid XDP action the same way as XDP_DROP
    https://git.kernel.org/netdev/net-next/c/975acc833c9f
  - [net-next,09/10] net: enetc: fix buffer leaks with XDP_TX enqueue rejections
    https://git.kernel.org/netdev/net-next/c/92ff9a6e578d
  - [net-next,10/10] net: enetc: apply the MDIO workaround for XDP_REDIRECT too
    https://git.kernel.org/netdev/net-next/c/24e393097171

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-04-17  0:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 21:22 [PATCH net-next 00/10] Fixups for XDP on NXP ENETC Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 01/10] net: enetc: remove redundant clearing of skb/xdp_frame pointer in TX conf path Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 02/10] net: enetc: rename the buffer reuse helpers Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 03/10] net: enetc: recycle buffers for frames with RX errors Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 04/10] net: enetc: stop XDP NAPI processing when build_skb() fails Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 05/10] net: enetc: remove unneeded xdp_do_flush_map() Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 06/10] net: enetc: increase TX ring size Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 07/10] net: enetc: use dedicated TX rings for XDP Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 08/10] net: enetc: handle the invalid XDP action the same way as XDP_DROP Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 09/10] net: enetc: fix buffer leaks with XDP_TX enqueue rejections Vladimir Oltean
2021-04-16 21:22 ` [PATCH net-next 10/10] net: enetc: apply the MDIO workaround for XDP_REDIRECT too Vladimir Oltean
2021-04-17  0:20 ` 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=161861881380.3813.7857023133457832186.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandru.marginean@nxp.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=po.liu@nxp.com \
    --cc=toke@redhat.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=yangbo.lu@nxp.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 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.