From: thunder7@xs4all.nl
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org, linux-kernel@vger.kernel.org
Subject: Re: documented Oops running big-endian reiserfs on parisc architecture
Date: Mon, 3 Sep 2001 12:52:18 +0200 [thread overview]
Message-ID: <20010903125218.A3192@middle.of.nowhere> (raw)
In-Reply-To: <20010902105538.A15344@middle.of.nowhere> <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk> <20010902.160441.92583890.davem@redhat.com> <20010903002514.X5126@parcelfarce.linux.theplanet.co.uk>
In-Reply-To: <20010903002514.X5126@parcelfarce.linux.theplanet.co.uk>
On Mon, Sep 03, 2001 at 12:25:14AM +0100, Matthew Wilcox wrote:
> On Sun, Sep 02, 2001 at 04:04:41PM -0700, David S. Miller wrote:
> > From: Matthew Wilcox <willy@debian.org>
> > Date: Sun, 2 Sep 2001 15:00:23 +0100
> >
> > On Sun, Sep 02, 2001 at 10:55:38AM +0200, thunder7@xs4all.nl wrote:
> > > ReiserFS version 3.6.25
> > > bonnie[163]: Unaligned data reference 28
> >
> > As it says, an unaligned data reference.
> >
> > BTW, you should not be OOPSing on this as unaligned references are
> > defined as completely normal, especially in the networking.
> >
> > Is it impossible to handle unaligned access traps properly on
> > parisc? If so, well you have some problems...
>
> No, we just haven't bothered to implement it yet. Not many people
> use IPX these days.
>
OK, well this seems to have opened quite a can of worms. Programming the
handling of unaligned access traps on parisc is quite above my
possibilities.
I did notice that mark_de_without_sd() in reiserfs_fs.h just calls the
ext2_{set|clear|test}_bit routines. If the host architecture should
handle that with unaligned addresses, obviously the exception for s390
should also go. The current source would make reiserfs slow on sparc as
well, if I understand correctly.
To solve this for parisc, I see two possibilities:
- rewrite asm/parisc/bitops.h to have the ext2_* routines handle
unaligned addresses. This would possibly be slowing down all aligned
access. Not so nice.
- rewrite reiserfs_fs.h to use it's own test/set/clear bit routines.
This would lose all the optimizations all specific architectures have
in their asm/*/bitops.h. Also not nice.
Keeping in mind that I don't know any parisc assembly, is there any way
I can help resolve this in an elegant manner?
Greetings,
Jurriaan
--
If all else fails, immortality can always be assured by spectacular error.
John Kenneth Galbraith
GNU/Linux 2.4.9-ac5 SMP/ReiserFS 2x1402 bogomips load av: 0.45 0.12 0.04
next prev parent reply other threads:[~2001-09-03 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-02 8:55 documented Oops running big-endian reiserfs on parisc architecture thunder7
2001-09-02 14:00 ` [parisc-linux] " Matthew Wilcox
2001-09-02 17:57 ` [SOLVED + PATCH]: " thunder7
2001-09-02 22:34 ` Richard Zidlicky
2001-09-02 23:08 ` David S. Miller
2001-09-02 23:29 ` [parisc-linux] Re: [SOLVED + PATCH]: documented Oops running big-endian reiserfs Alan Cox
2001-09-04 1:38 ` [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture Jeff Mahoney
2001-09-02 23:04 ` [parisc-linux] " David S. Miller
2001-09-02 23:25 ` Matthew Wilcox
2001-09-02 23:26 ` David S. Miller
2001-09-02 23:31 ` Alan Cox
2001-09-03 10:52 ` thunder7 [this message]
2001-09-03 10:25 ` Hans Reiser
2001-09-03 14:30 ` [parisc-linux] " Matthew Wilcox
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=20010903125218.A3192@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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