public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [DOCUMENTATION] Revised Unreliable Kernel Locking Guide
Date: Mon, 15 Dec 2003 16:17:24 +1100	[thread overview]
Message-ID: <20031215060838.A6F712C21D@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 12 Dec 2003 22:16:24 CDT." <Pine.LNX.4.58.0312122203090.23752@montezuma.fsmlabs.com>

In message <Pine.LNX.4.58.0312122203090.23752@montezuma.fsmlabs.com> you write:
> I think he could also add that local_irq_disable() also disables
> preemption implicitely.

True, but I don't actually mention preemption very much at all, except
in RCU.  That belongs more in the Unreliable Guide To Kernel Hacking,
IMHO.

Revising which is next weeks' job.

> Small nit, it's 'current'

Thanks fixed!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-12-15  6:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12  5:24 [DOCUMENTATION] Revised Unreliable Kernel Locking Guide Rusty Russell
2003-12-12 15:44 ` Dave Jones
2003-12-12 16:25   ` Keith Owens
2003-12-12 18:25     ` Dave Jones
2003-12-13  0:28       ` Keith Owens
2003-12-12 21:05   ` Rob Love
2003-12-15  2:28   ` Rusty Russell
2003-12-12 19:35 ` Paul E. McKenney
2003-12-13  3:16   ` Zwane Mwaikambo
2003-12-15  5:17     ` Rusty Russell [this message]
2003-12-15  5:17   ` Rusty Russell
2003-12-15 22:22     ` Paul E. McKenney
2003-12-16  6:32       ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2003-12-13  3:15 Manfred Spraul

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=20031215060838.A6F712C21D@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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