netdev - Re: [PATCH net-next 1/2] tcp-zerocopy: Return inq along with tcp 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]

Message-Id: <20200216.192517.1439206340999549107.davem@davemloft.net>
Date:   Sun, 16 Feb 2020 19:25:17 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     arjunroy.kdev@...il.com
Cc:     netdev@...r.kernel.org, arjunroy@...gle.com, soheil@...gle.com,
        edumazet@...gle.com
Subject: Re: [PATCH net-next 1/2] tcp-zerocopy: Return inq along with tcp
 receive zerocopy.

From: Arjun Roy <arjunroy.kdev@...il.com>
Date: Fri, 14 Feb 2020 15:30:49 -0800

> From: Arjun Roy <arjunroy@...gle.com>
> 
> This patchset is intended to reduce the number of extra system calls
> imposed by TCP receive zerocopy. For ping-pong RPC style workloads,
> this patchset has demonstrated a system call reduction of about 30%
> when coupled with userspace changes.
> 
> For applications using edge-triggered epoll, returning inq along with
> the result of tcp receive zerocopy could remove the need to call
> recvmsg()=-EAGAIN after a successful zerocopy. Generally speaking,
> since normally we would need to perform a recvmsg() call for every
> successful small RPC read via TCP receive zerocopy, returning inq can
> reduce the number of system calls performed by approximately half.
> 
> Signed-off-by: Arjun Roy <arjunroy@...gle.com>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Signed-off-by: Soheil Hassas Yeganeh <soheil@...gle.com>

Applied.