From: Paul Clements <Paul.Clements@SteelEye.com>
To: Matthew Mitchell <matthew@geodev.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 11:04:40 -0400 [thread overview]
Message-ID: <3EE89688.71AFFAB6@SteelEye.com> (raw)
In-Reply-To: 3EE89211.4030805@geodev.com
Matthew Mitchell wrote:
> Paul Clements wrote:
> > 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.
If you just wanted to rip out the superblock code from the 2.5 md.c and
use that in 2.4, it probably wouldn't be too bad. The superblock
handling code has been improved and modularized quite a bit, and the md
driver can now handle various different superblock formats.
--
Paul
next prev parent reply other threads:[~2003-06-12 15:04 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
2003-06-12 15:04 ` Paul Clements [this message]
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=3EE89688.71AFFAB6@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=3tcdgwg3@prodigy.net \
--cc=linux-raid@vger.kernel.org \
--cc=matthew@geodev.com \
--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).