From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vs166246.vserver.de (bu3sch.de [62.75.166.246]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 5AF72B7BCF for ; Tue, 27 Oct 2009 06:30:37 +1100 (EST) From: Michael Buesch To: linuxppc-dev@lists.ozlabs.org Subject: Re: Network Stack SKB Reallocation Date: Mon, 26 Oct 2009 20:13:50 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200910262013.52458.mb@bu3sch.de> Cc: Jonathan Haws List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Monday 26 October 2009 19:43:00 Jonathan Haws wrote: > Quick question about the network stack in general: > > Does the stack itself release an SKB allocated by the device driver back to the heap upstream, or does it require that the device driver handle that? There's the concept of passing responsibilities for the frames between the networking layers. So the driver passes the frame and all responsibilities to the networking stack. So if the networking stack accepts the packet in the first place, it needs to free it (or pass it to somebody else to take care of). -- Greetings, Michael.