From: patchwork-bot+netdevbpf@kernel.org
To: Arjun Roy <arjunroy.kdev@gmail.com>
Cc: netdev@vger.kernel.org, arjunroy@google.com, edumazet@google.com,
soheil@google.com, kuba@kernel.org, akpm@linux-foundation.org,
dsahern@kernel.org, davem@davemloft.net, linux-mm@kvack.org,
pabeni@redhat.com
Subject: Re: [net-next,v2] tcp: Use per-vma locking for receive zerocopy
Date: Sun, 18 Jun 2023 10:20:19 +0000 [thread overview]
Message-ID: <168708361952.30416.4165448356299935816.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230616193427.3908429-1-arjunroy.kdev@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 16 Jun 2023 12:34:27 -0700 you wrote:
> From: Arjun Roy <arjunroy@google.com>
>
> Per-VMA locking allows us to lock a struct vm_area_struct without
> taking the process-wide mmap lock in read mode.
>
> Consider a process workload where the mmap lock is taken constantly in
> write mode. In this scenario, all zerocopy receives are periodically
> blocked during that period of time - though in principle, the memory
> ranges being used by TCP are not touched by the operations that need
> the mmap write lock. This results in performance degradation.
>
> [...]
Here is the summary with links:
- [net-next,v2] tcp: Use per-vma locking for receive zerocopy
https://git.kernel.org/netdev/net-next/c/7a7f09463534
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:[~2023-06-18 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 19:34 [net-next,v2] tcp: Use per-vma locking for receive zerocopy Arjun Roy
2023-06-18 10:20 ` patchwork-bot+netdevbpf [this message]
2023-07-06 19:43 ` Matthew Wilcox
2023-07-07 15:44 ` Eric Dumazet
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=168708361952.30416.4165448356299935816.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arjunroy.kdev@gmail.com \
--cc=arjunroy@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.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.