Received: with ECARTIS (v1.0.0; list netdev); Tue, 09 Nov 2004 17:11:40 -0800 (PST) Received: from kaber.coreworks.de ([62.206.217.67]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id iAA1BZCs007573 for ; Tue, 9 Nov 2004 17:11:36 -0800 Received: from localhost ([127.0.0.1]) by kaber.coreworks.de with esmtp (Exim 4.34) id 1CRh0T-00074D-So; Wed, 10 Nov 2004 02:10:41 +0100 Message-ID: <41916A91.3080107@trash.net> Date: Wed, 10 Nov 2004 02:10:41 +0100 From: Patrick McHardy User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041008 Debian/1.7.3-5 X-Accept-Language: en MIME-Version: 1.0 To: Thomas Graf CC: "David S. Miller" , Herbert Xu , netdev@oss.sgi.com Subject: Re: request_module while holding rtnl semaphore References: <41899DCF.3050804@trash.net> <20041109161126.376f755c.davem@davemloft.net> <20041110010113.GJ31969@postel.suug.ch> In-Reply-To: <20041110010113.GJ31969@postel.suug.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 11660 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: kaber@trash.net Precedence: bulk X-list: netdev Content-Length: 350 Lines: 13 Thomas Graf wrote: >Sounds reasonable for the sch_api.c and cls_api.c case but >will get very nasty for act_api as you noted and any further sub >layers that might be added in the future. (The classifier I'm >working on is such a case.) > Can you please show an example of a case where this is needed ? Just to help me understand. Regards Patrick