Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 9 Jul 2002 07:41:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 9 Jul 2002 07:41:33 -0400 Received: from chaos.analogic.com ([204.178.40.224]:41348 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Tue, 9 Jul 2002 07:41:32 -0400 Date: Tue, 9 Jul 2002 07:45:45 -0400 (EDT) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Thunder from the hill cc: Oliver Neukum , Keith Owens , Patrick Mochel , linux-kernel@vger.kernel.org Subject: Re: Driverfs updates In-Reply-To: Message-ID: 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: 1242 Lines: 36 On Tue, 9 Jul 2002, Thunder from the hill wrote: > Hi, > > On Tue, 9 Jul 2002, Oliver Neukum wrote: > > -It is slow. > > I wouldn't call it any fast when I think about the idea that 31 of my CPUs > on Hawkeye shall be stopped because I unload a module. Sometimes at high > noon my server (Hawkeye) can hardly keep up all the traffic. Just imagine > a module would be unloaded then! That's the problem I'm having with it. > > What should make a lock for parts of the kernel slower than a lock for > the _whole_ kernel? > > Regards, > Thunder The module unload is to be used only during module development (so you don't have to re-boot), as was the very first conjecture in this thread. The current 'auto-unload' in some distributions like RedHat will go away. The only way a module will be unloaded is if you, as root, unload it. Cheers, Dick Johnson Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). Windows-2000/Professional isn't. - 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/