From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sowmini Varadhan Subject: Re: [PATCH net-next 2/7] rds: hold a sock ref from rds_message to the rds_sock Date: Thu, 25 Jan 2018 10:35:27 -0500 Message-ID: <20180125153527.GJ18181@oracle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Network Development , David Miller , rds-devel@oss.oracle.com, santosh.shilimkar@oracle.com To: Willem de Bruijn Return-path: Received: from aserp2120.oracle.com ([141.146.126.78]:52586 "EHLO aserp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751244AbeAYPfl (ORCPT ); Thu, 25 Jan 2018 10:35:41 -0500 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On (01/25/18 15:44), Willem de Bruijn wrote: > > This patch manages the m_rs assignment in the rds_message with > > the necessary refcount book-keeping. > > You may alos be able to do the same as tcp zerocopy and > hold an sk reference on the notification skb. We tether the notification skb to the rds socket after the refcount on the rds_message goes to zero, so we already have a ref from the sk to the notification skb, If we kept a refcount of all notification skb's (even the ones that are not ready to be unpinned yet) on the sk, then we have additional complexity trying to figure out which skb's are ready for notification at any point, so not sure it would make things simpler.. --Sowmini