LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Liu Dave-r63238 <DaveLiu@freescale.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: RE: atomic operations in user space
Date: Wed, 30 Aug 2006 01:33:33 -0500	[thread overview]
Message-ID: <20060830063333.GA16468@pb15.lixom.net> (raw)
In-Reply-To: <995B09A8299C2C44B59866F6391D263511BB62@zch01exm21.fsl.freescale.net>

On Wed, Aug 30, 2006 at 10:55:39AM +0800, Liu Dave-r63238 wrote:

> Can we do atomic operation in user space as kernel space?

Yes.


-Olof

  reply	other threads:[~2006-08-30  6:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  2:17 atomic operations in user space Liu Dave-r63238
2006-08-30  2:27 ` Liu Dave-r63238
2006-08-30  2:40   ` Li Yang-r58472
2006-08-30  2:28 ` Li Yang-r58472
2006-08-30  2:42   ` Liu Dave-r63238
2006-08-30  2:52     ` Li Yang-r58472
2006-08-30  2:55       ` Liu Dave-r63238
2006-08-30  6:33         ` Olof Johansson [this message]
2006-08-30  7:00           ` Atomic operations in user space: Yes but No Benjamin Herrenschmidt

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=20060830063333.GA16468@pb15.lixom.net \
    --to=olof@lixom.net \
    --cc=DaveLiu@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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