From: Keith Whitwell <keith@tungstengraphics.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.18: DRM + cmpxchg issues
Date: Tue, 28 May 2002 09:13:04 +0100 [thread overview]
Message-ID: <3CF33C10.1090302@tungstengraphics.com> (raw)
Adam,
I expect the answer is that we need to dig out the old one.
Previously I don't think the full cmpxchg semantics werere required unless the
box is smp -- there's no case where atomic operations are required for
hardware interaction, for example. ...
Probably this changed with preempt, though, so we need one even on UP boxes...
Keith
next reply other threads:[~2002-05-28 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 8:13 Keith Whitwell [this message]
2002-05-29 0:59 ` linux-2.5.18: DRM + cmpxchg issues george anzinger
2002-05-29 7:23 ` Keith Whitwell
-- strict thread matches above, loose matches on Subject: below --
2002-05-26 8:32 Adam J. Richter
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=3CF33C10.1090302@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=linux-kernel@vger.kernel.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 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.