mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: maxk@qualcomm.com, linux-kernel@vger.kernel.org
Subject: Re: Another idea for simplifying locking in kernel/module.c
Date: Sat, 11 Jan 2003 14:53:23 +1100	[thread overview]
Message-ID: <20030111050918.C06212C2DE@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 10 Jan 2003 03:16:30 -0800." <200301101116.DAA03752@baldur.yggdrasil.com>

In message <200301101116.DAA03752@baldur.yggdrasil.com> you write:
> I wrote:
> >On Thu, 09 Jan 2003, Max Krasnyansky wrote:
> >>We have to be able to call try_module_get() from interrupt context.
> 
> >	Where?  Why?  Please show me one or more examples.
> 
> 	Come to think of it, I don't think you even have to answer
> that question.  You should be able to use my try_module_get() from
> interrupt context.  It never blocks.

Yes, your try_module_get just gets spurious failures on SMP, as well
as thrashing the cacheline (why bother with one counter per CPU
then?).

I guess I just don't understand your solution?

Sorry,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-01-11  5:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 11:16 Adam J. Richter
2003-01-11  3:53 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 12:18 Adam J. Richter
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  8:53 Adam J. Richter
2003-01-09 20:41 ` Max Krasnyansky
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=20030111050918.C06212C2DE@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.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

Powered by JetHome