From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:32790 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbeB0TTm (ORCPT ); Tue, 27 Feb 2018 14:19:42 -0500 Date: Tue, 27 Feb 2018 14:19:38 -0500 (EST) Message-Id: <20180227.141938.143210324321316647.davem@davemloft.net> To: sowmini.varadhan@oracle.com Cc: netdev@vger.kernel.org Subject: Re: [PATCH RESEND V3 net-next 0/3] RDS: optimized notification for zerocopy completion From: David Miller In-Reply-To: References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: From: Sowmini Varadhan 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.