netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	toke@redhat.com, xuanzhuo@linux.alibaba.com,
	henqqi@linux.alibaba.com
Subject: Re: [PATCH] veth: Avoid drop packets when xdp_redirect performs
Date: Wed, 02 Nov 2022 12:10:15 +0000	[thread overview]
Message-ID: <166739101532.14028.3067823596353159397.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221031061922.124992-1-hengqi@linux.alibaba.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 31 Oct 2022 14:19:22 +0800 you wrote:
> From: Heng Qi <henqqi@linux.alibaba.com>
> 
> In the current processing logic, when xdp_redirect occurs, it transmits
> the xdp frame based on napi.
> 
> If napi of the peer veth is not ready, the veth will drop the packets.
> This doesn't meet our expectations.
> 
> [...]

Here is the summary with links:
  - veth: Avoid drop packets when xdp_redirect performs
    https://git.kernel.org/netdev/net-next/c/2e0de6366ac1

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



      reply	other threads:[~2022-11-02 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  6:19 [PATCH] veth: Avoid drop packets when xdp_redirect performs Heng Qi
2022-11-02 12:10 ` 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=166739101532.14028.3067823596353159397.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hengqi@linux.alibaba.com \
    --cc=henqqi@linux.alibaba.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@redhat.com \
    --cc=xuanzhuo@linux.alibaba.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).