From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
Cc: alacrityvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Alacrityvm-devel] alacrityvm-next: clearly specify ioq endianness
Date: Wed, 09 Dec 2009 13:17:00 -0500 [thread overview]
Message-ID: <4B1FE99C.9070205@gmail.com> (raw)
In-Reply-To: <1260305854-31472-1-git-send-email-iws@ovro.caltech.edu>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On 12/8/09 3:57 PM, Ira W. Snyder wrote:
>
> This is a respin of the previous patch series against alacrityvm.git's
> linux-next branch, to facilitate easier merging with the linux-next tree.
>
> The SHM_SIGNAL and IOQ code is meant to be used for communication channels
> between systems with different bit widths and operating systems.
> Conceivably, this could include systems with different endianness as well,
> for example, using QEMU on x86 to emulate a powerpc.
>
> This patch series annotates all shared structures as little endian, and
> fixes up all users. This means that there is no overhead in the most common
> case, x86-on-x86. The byteswaps compile out.
>
> [RESEND: added LKML to CC per Greg Haskins' request]
Applied, thanks!
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
prev parent reply other threads:[~2009-12-09 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 20:57 alacrityvm-next: clearly specify ioq endianness Ira W. Snyder
2009-12-08 20:57 ` [PATCH] vbus: fix lots of sparse "dubious signed bitfield" warnings Ira W. Snyder
2009-12-08 20:57 ` [PATCH] vbus: pci-bridge: fix sparse warnings Ira W. Snyder
2009-12-08 20:57 ` [PATCH] vbus-enet: " Ira W. Snyder
2009-12-08 20:57 ` [PATCH] shm_signal: clearly specify endianness Ira W. Snyder
2009-12-08 20:57 ` [PATCH] ioq: " Ira W. Snyder
2009-12-09 18:17 ` Gregory Haskins [this message]
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=4B1FE99C.9070205@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=iws@ovro.caltech.edu \
--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.