From: Oliver Neukum <oliver@neukum.name>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Thunder from the hill <thunder@ngforever.de>,
Keith Owens <kaos@ocs.com.au>, Patrick Mochel <mochel@osdl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Driverfs updates
Date: Tue, 9 Jul 2002 19:05:28 +0200 [thread overview]
Message-ID: <200207091905.28401.oliver@neukum.name> (raw)
In-Reply-To: <Pine.LNX.4.44.0207090502510.10105-100000@hawkeye.luckynet.adm>
Am Dienstag, 9. Juli 2002 13:08 schrieb Thunder from the hill:
> 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?
Because you unload modules rarely, but you'd take the lock millions of times
in vain.
Regards
Oliver
next prev parent reply other threads:[~2002-07-09 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 18:41 Patrick Mochel
2002-07-08 23:33 ` Keith Owens
2002-07-08 23:52 ` Thunder from the hill
2002-07-09 0:09 ` Keith Owens
2002-07-09 8:30 ` Oliver Neukum
2002-07-09 11:08 ` Thunder from the hill
2002-07-09 11:45 ` Richard B. Johnson
2002-07-09 12:20 ` David D. Hagood
2002-07-09 12:33 ` Thunder from the hill
2002-07-09 14:43 ` jbradford
2002-07-10 7:15 ` jw schultz
2002-07-09 17:05 ` Oliver Neukum [this message]
2002-07-10 0:43 ` Pavel Machek
2002-07-09 16:56 ` Patrick Mochel
2002-07-09 23:29 ` Keith Owens
2002-07-10 20:02 ` Patrick Mochel
2002-07-11 0:40 ` John Alvord
2002-07-18 18:11 driverfs updates Patrick Mochel
2002-07-18 18:33 ` Greg KH
2002-07-18 19:57 ` Patrick Mochel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207091905.28401.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=thunder@ngforever.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®