linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Mitchell <matthew@geodev.com>
To: Paul Clements <Paul.Clements@SteelEye.com>
Cc: Mike Tran <mhtran@us.ibm.com>, 3tcdgwg3 <3tcdgwg3@prodigy.net>,
	linux-raid@vger.kernel.org
Subject: Re: Move md raid5 from intel to sparc?
Date: Thu, 12 Jun 2003 09:45:37 -0500	[thread overview]
Message-ID: <3EE89211.4030805@geodev.com> (raw)
In-Reply-To: <3EE78D29.2EEFA36A@SteelEye.com>

Paul Clements wrote:
> Mike Tran wrote:
> 
>>On Wed, 2003-06-11 at 14:31, 3tcdgwg3 wrote:
>>
>>>I am doing a sparc thingin. I have to build
>>>the disk images on a x86 system, and move the
>>>disk to my sparc, for debug/test.  Everhting works
>>>fine, except the MD's SB.  I tweaked a bit on MD
>>>driver, then everything is good.  I would think that
>>>MD should take care the SB format in next release.
>>>
>>
>>This work should start from the MD kernel driver.  That is the MD driver
>>has to write the SB in one known format and converts the SB to the
>>native cpu after reading it from disk.  Next, the MD tools (mdadm,
>>mdreconf, etc.) will need to follow.
>>
>>Neil B, Do you have this work item in mind?
> 
> 
> Neil's new version 1 superblock, which is present in the 2.5 kernel,
> addresses the byte ordering issues that are a problem in the current
> 0.90 superblock of the 2.4 md driver.
> The new superblock code stores all numeric values in little endian
> on-disk and converts them to CPU endianness before use.

Any possibility of a backport?  If it's not too hairy I don't mind 
attempting it myself, but I haven't even looked at md in 2.5.

-- 
Matthew Mitchell
Systems Programmer/Administrator            matthew@geodev.com
Geophysical Development Corporation         phone 713 782 1234
1 Riverway Suite 2100, Houston, TX  77056     fax 713 782 1829


  reply	other threads:[~2003-06-12 14:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 15:02 Move md raid5 from intel to sparc? Matthew Mitchell
2003-06-11 16:57 ` Mike Tran
2003-06-11 18:03   ` Matthew Mitchell
2003-06-11 19:08     ` Matt Stegman
2003-06-11 20:44       ` Matti Aarnio
2003-06-11 21:16         ` Tom Vier
2003-06-11 19:17     ` Mike Tran
2003-06-11 19:31       ` 3tcdgwg3
2003-06-11 19:50         ` Mike Tran
2003-06-11 20:12           ` Paul Clements
2003-06-12 14:45             ` Matthew Mitchell [this message]
2003-06-12 15:04               ` Paul Clements
2003-06-13  5:29               ` Neil Brown
2003-06-11 19:24 ` Cal Webster

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=3EE89211.4030805@geodev.com \
    --to=matthew@geodev.com \
    --cc=3tcdgwg3@prodigy.net \
    --cc=Paul.Clements@SteelEye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mhtran@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).