Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Gray <mark.d.gray@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
	dan.carpenter@oracle.com, pravin.ovn@gmail.com, fbl@sysclose.org
Subject: Re: [PATCH net-next v2] openvswitch: Introduce per-cpu upcall dispatch
Date: Fri, 16 Jul 2021 18:10:04 +0000	[thread overview]
Message-ID: <162645900480.11090.2397559408489186888.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210715122754.1240288-1-mark.d.gray@redhat.com>

Hello:

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

On Thu, 15 Jul 2021 08:27:54 -0400 you wrote:
> The Open vSwitch kernel module uses the upcall mechanism to send
> packets from kernel space to user space when it misses in the kernel
> space flow table. The upcall sends packets via a Netlink socket.
> Currently, a Netlink socket is created for every vport. In this way,
> there is a 1:1 mapping between a vport and a Netlink socket.
> When a packet is received by a vport, if it needs to be sent to
> user space, it is sent via the corresponding Netlink socket.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] openvswitch: Introduce per-cpu upcall dispatch
    https://git.kernel.org/netdev/net-next/c/b83d23a2a38b

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-07-16 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 12:27 Mark Gray
2021-07-15 22:57 ` Pravin Shelar
2021-07-16  7:19   ` Mark Gray
2021-07-16 18: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=162645900480.11090.2397559408489186888.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=dev@openvswitch.org \
    --cc=fbl@sysclose.org \
    --cc=mark.d.gray@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pravin.ovn@gmail.com \
    --subject='Re: [PATCH net-next v2] openvswitch: Introduce per-cpu upcall dispatch' \
    /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

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).