netdev - Re: [net-next,v2] tcp: Use per-vma locking for receive zerocopy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Sun, 18 Jun 2023 10:20:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Arjun Roy <arjunroy.kdev@...il.com>
Cc: netdev@...r.kernel.org, arjunroy@...gle.com, edumazet@...gle.com,
 soheil@...gle.com, kuba@...nel.org, akpm@...ux-foundation.org,
 dsahern@...nel.org, davem@...emloft.net, linux-mm@...ck.org,
 pabeni@...hat.com
Subject: Re: [net-next,v2] tcp: Use per-vma locking for receive zerocopy

Hello:

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

On Fri, 16 Jun 2023 12:34:27 -0700 you wrote:
> From: Arjun Roy <arjunroy@...gle.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