public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: "Tillier, Fabian" <ftillier@infiniconsys.com>
Cc: linux-kernel@vger.kernel.org, infiniband-general@lists.sourceforge.net
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the Linux kernel
Date: Sat, 7 Feb 2004 02:54:04 +0000	[thread overview]
Message-ID: <20040207025404.GJ12503@mail.shareable.org> (raw)
In-Reply-To: <08628CA53C6CBA4ABAFB9E808A5214CB01DB96A4@mercury.infiniconsys.com>

Tillier, Fabian wrote:
> Further, comments in the x86 code base indicated that only 24-bits
> are actually valid (probably from some i386 limitation that is no
> longer relevant).

It is because of the Sparc architecture.  I think Sparc doesn't (or
perhaps didn't) have atomic operations, so a cunning hack is used to
simulate them.

-- Jamie

  parent reply	other threads:[~2004-02-07  2:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 18:31 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 18:40 ` Greg KH
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07  2:54 ` Jamie Lokier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:16 [Infiniband-general] Getting an Infiniband access layer in the linux kernel Woodruff, Robert J
2004-02-05 21:54 ` Greg KH
2004-02-06 23:20   ` Jamie Lokier
2004-02-05 19:44 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 20:16 ` Greg KH
2004-02-05 19:38 [Infiniband-general] Getting an Infiniband access layer in the linux kernel King, Steven R
2004-02-05 21:51 ` Greg KH
2004-02-05 19:31 Raj, Ashok
     [not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 18:34 Raj, Ashok
     [not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` Greg KH
2004-02-04  4:53 Woodruff, Robert J
2004-02-04  2:01 Woodruff, Robert J
2004-02-04  4:08 ` Troy Benjegerdes
2004-02-04  0:17 Woodruff, Robert J
2004-02-04  1:03 ` Greg KH
2004-02-03 16:45 Woodruff, Robert J
2004-02-04 11:26 ` Masanori ITOH
2004-02-02 23:58 Woodruff, Robert J
2004-02-03  0:56 ` Greg KH
2004-02-03  1:38 ` Masanori ITOH
2004-02-03 22:37 ` Troy Benjegerdes

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=20040207025404.GJ12503@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=ftillier@infiniconsys.com \
    --cc=infiniband-general@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox