The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@minantech.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	akpm@osdl.org, Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Document futex PI design
Date: Wed, 10 May 2006 15:46:00 +0300	[thread overview]
Message-ID: <20060510124600.GN5319@minantech.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0605100657510.2485@gandalf.stny.rr.com>

On Wed, May 10, 2006 at 06:59:49AM -0400, Steven Rostedt wrote:
> +lock	 - In this document from now on, the term lock and spin lock will
> +	   be synonymous.  These are locks that are used for SMP as well
> +	   as turning off preemption to protect areas of code on SMP machines.
Should the last SMP be UP?

--
			Gleb.

  reply	other threads:[~2006-05-10 12:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 13:55 [PATCH] Document futex PI design Steven Rostedt
2006-05-10  7:37 ` Steven Rostedt
2006-05-10  8:33   ` Steven Rostedt
2006-05-10 10:17     ` Ingo Molnar
2006-05-10 10:59       ` Steven Rostedt
2006-05-10 12:46         ` Gleb Natapov [this message]
2006-05-10 13:09           ` Steven Rostedt
2006-05-10 13:27           ` [PATCH -mm 00/02] update to " Steven Rostedt
2006-05-10 13:30             ` [PATCH -mm 01/02] Remove tabs from " Steven Rostedt
2006-05-10 13:36             ` [PATCH -mm 02/02] Redefine "lock" in " Steven Rostedt
2006-05-13 17:01             ` [PATCH -mm 00/02] update to " Randy.Dunlap
2006-05-13 17:07               ` Steven Rostedt
2006-05-13 17:15                 ` Randy.Dunlap
2006-05-14  3:14         ` [PATCH] " Randy.Dunlap
2006-05-14 14:00           ` Steven Rostedt
2006-05-14 18:28             ` Randy.Dunlap
2006-05-15  6:25               ` Steven Rostedt
2006-05-15  7:21           ` Steven Rostedt
2006-05-15  9:09             ` Steven Rostedt

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=20060510124600.GN5319@minantech.com \
    --to=gleb@minantech.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.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