netdev - Re: [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for zerocopy completion

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20180227.141938.143210324321316647.davem@davemloft.net>
Date:   Tue, 27 Feb 2018 14:19:38 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     sowmini.varadhan@...cle.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for
 zerocopy completion

From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Tue, 27 Feb 2018 09:52:41 -0800

> Resending with acked-by additions: previous attempt does not show
> up in Patchwork. This time with a new mail Message-Id.
> 
> RDS applications use predominantly request-response, transacation
> based IPC, so that ingress and egress traffic are well-balanced,
> and it is possible/desirable to reduce system-call overhead by
> piggybacking the notifications for zerocopy completion response
> with data.
> 
> Moreover, it has been pointed out that socket functions block
> if sk_err is non-zero, thus if the RDS code does not plan/need
> to use sk_error_queue path for completion notification, it
> is preferable to remove the sk_errror_queue related paths in
> RDS.
> 
> Both of these goals are implemented in this series.
> 
> v2: removed sk_error_queue support
> v3: incorporated additional code review comments (details in each patch)

Series applied, thank you.