From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 0/14] skb fragment API: convert network drivers (part III) Date: Thu, 22 Sep 2011 16:05:45 -0400 (EDT) Message-ID: <20110922.160545.526551451487549432.davem@davemloft.net> References: <1316677996.23371.10.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Ian.Campbell@citrix.com Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:48565 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061Ab1IVUFu (ORCPT ); Thu, 22 Sep 2011 16:05:50 -0400 In-Reply-To: <1316677996.23371.10.camel@zakaz.uk.xensource.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Ian Campbell Date: Thu, 22 Sep 2011 08:53:16 +0100 > The following series converts the third batch of network drivers to the > SKB pages fragment API introduced in 131ea6675c76. I expect there will > be ~4 similarly sized batches to convert all the drivers over. > > This is part of my series to enable visibility into SKB paged fragment's > lifecycles, [0] contains some more background and rationale but > basically the completed series will allow entities which inject pages > into the networking stack to receive a notification when the stack has > really finished with those pages (i.e. including retransmissions, > clones, pull-ups etc) and not just when the original skb is finished > with, which is beneficial to many subsystems which wish to inject pages > into the network stack without giving up full ownership of those page's > lifecycle. It implements something broadly along the lines of what was > described in [1]. ALl applied, thanks Ian.