public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andi Kleen <ak@muc.de>
Cc: davem@redhat.com, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, paul.mckenney@us.ibm.com,
	andrea@suse.de
Subject: Re: 8-CPU (SMP) #s for lockfree rtcache
Date: Wed, 29 May 2002 14:44:56 +1000	[thread overview]
Message-ID: <20020529144456.52c1bc1d.rusty@rustcorp.com.au> (raw)
In-Reply-To: <m3bsb06zt7.fsf@averell.firstfloor.org>

On 28 May 2002 17:45:56 +0200
Andi Kleen <ak@muc.de> wrote:

> "David S. Miller" <davem@redhat.com> writes:
> 
> >    From: Dipankar Sarma <dipankar@in.ibm.com>
> >    Date: Tue, 28 May 2002 18:28:06 +0530
> >    
> >    Well, the last time RCU was discussed, Linus said that he would
> >    like to see someplace where RCU clearly helps.
> > 
> > Alexey and I are in firm agreement that the routing cache
> > clearly benefits from RCU.
> 
> The next obvious benefitor IMHO is module unloading.

There is a much bigger question here, which is "are modules first class
citizens"?  Doing it properly turns us into a poor-man's microkernel.
We would standardize our registration interfaces (similar to the standard
notifier.h), and have them all do the inc and decs.

OTOH, if you treat module removal as a CONFIG_DEBUG_KERNEL thing, life
becomes much much simpler.

I have the code, I'll be serious about it in ~2 months.
Rusty.
-- 
   there are those who do and those who hang on and you don't see too
   many doers quoting their contemporaries.  -- Larry McVoy

  parent reply	other threads:[~2002-05-29  4:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 11:41 8-CPU (SMP) #s for lockfree rtcache Dipankar Sarma
2002-05-28 11:25 ` David S. Miller
2002-05-28 12:58   ` Dipankar Sarma
2002-05-28 12:40     ` David S. Miller
2002-05-28 15:45       ` Andi Kleen
2002-05-28 17:03         ` Alan Cox
2002-05-28 16:34           ` Andi Kleen
2002-05-28 18:10             ` Alan Cox
2002-05-28 17:24               ` Andi Kleen
2002-05-29  4:44         ` Rusty Russell [this message]
2002-05-28 15:49     ` Robert Love
2002-05-28 16:25       ` Dipankar Sarma
2002-05-28 17:09         ` Dipankar Sarma
2002-05-29 17:44       ` kuznet
2002-06-03 12:08       ` Dipankar Sarma
  -- strict thread matches above, loose matches on Subject: below --
2002-05-28 19:57 Dipankar Sarma

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=20020529144456.52c1bc1d.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=ak@muc.de \
    --cc=andrea@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.mckenney@us.ibm.com \
    --cc=torvalds@transmeta.com \
    /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