All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another idea for simplifying locking in kernel/module.c
Date: Tue, 7 Jan 2003 00:53:15 -0800	[thread overview]
Message-ID: <200301070853.AAA04065@baldur.yggdrasil.com> (raw)

I wrote:
>        Here is a way to replace all of the specialized "stop CPU"
>locking code in kernel/module.c with an rw_semaphore by using
>down_read_trylock in try_module_get() and down_write when beginning to
>unload the module.
>
>        The following UNTESTED patch, a net deletion of 136 lines,

	I am running that patch now on two computers.  It seems to
be OK.

	Rusty, I'd be interested in knowing what you think of the
patch (likewise for other lkml readers).

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2003-01-07  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  8:53 Adam J. Richter [this message]
2003-01-09 20:41 ` Another idea for simplifying locking in kernel/module.c Max Krasnyansky
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 12:18 Adam J. Richter
2003-01-10 11:16 Adam J. Richter
2003-01-11  3:53 ` Rusty Russell
2003-01-10  9:38 Adam J. Richter
2003-01-10  9:10 Adam J. Richter
2003-01-10  9:38 ` Andre Hedrick
2003-01-10 10:15   ` Rusty Russell
2003-01-11 14:46   ` Bill Davidsen
2003-01-10 10:11 ` Rusty Russell
2003-01-07  2:19 Adam J. Richter
2003-01-08 11:46 ` Rusty Russell

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=200301070853.AAA04065@baldur.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.