Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261775AbVAMXVx (ORCPT ); Thu, 13 Jan 2005 18:21:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261770AbVAMXTr (ORCPT ); Thu, 13 Jan 2005 18:19:47 -0500 Received: from ns1.coraid.com ([65.14.39.133]:28078 "EHLO coraid.com") by vger.kernel.org with ESMTP id S261823AbVAMXNi (ORCPT ); Thu, 13 Jan 2005 18:13:38 -0500 To: Andi Kleen Cc: Jens Axboe , Linux Kernel List , jgarzik@pobox.com Subject: Re: [BUG] ATA over Ethernet __init calling __exit References: <20050113000949.A7449@flint.arm.linux.org.uk> <20050113085035.GC2815@suse.de> <87is616oi2.fsf@coraid.com> <20050113215346.GB1504@muc.de> <87ekgp567u.fsf@coraid.com> <20050113224832.GA19673@muc.de> From: Ed L Cashin Date: Thu, 13 Jan 2005 17:59:09 -0500 Message-ID: <87is613phe.fsf@coraid.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1112 Lines: 33 Andi Kleen writes: > On Thu, Jan 13, 2005 at 05:12:21PM -0500, Ed L Cashin wrote: > >> It seems rash to make the change now, because there is no need for it. > > It would be better to future proof the driver at least a bit. > >> >> For the skbuffs, we could use a mempool with GFP_NOIO allocation and >> then skb_get them before the network layer ever sees them. We already >> keep track of the packets that we've sent out, so we'll just keep a >> pointer to the skbuffs. > > That won't work because you don't know when the driver is done with it. > > There is a callback, but it's already used by socket buffer management The destructor member of struct sk_buff, right? > (if you don't use a socket it may be usable) You mean a struct sock? No, we don't use that because we're not IP. Thanks for the lead. -- Ed L Cashin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/