Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@mvista.com>
To: linux-mips <linux-mips@oss.sgi.com>
Subject: XFS
Date: 12 Mar 2002 17:29:11 -0800	[thread overview]
Message-ID: <1015982952.5196.62.camel@zeus> (raw)

Thanks to everyone who sent me suggestions and help on how they got xfs
working on mips.

I tried the split patches on a 2.4.18 kernel, compiled with a 2.95.3
compiler, and the kernel crashes consistently when running bonnie++. 
The same kernel compiled with a 3.0.1 based compiler seems to work fine.
I've ran bonnie++ a few times, as well as other conventional tests. I
need to do a lot more testing before I'm convinced that xfs is rock
solid on mips, but it appears that the compiler problems described on
the web site are for real.

Pete

             reply	other threads:[~2002-03-13  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13  1:29 Pete Popov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-08 18:22 xfs Pete Popov
2002-03-08 18:42 ` xfs Seth Mos
2002-03-08 19:22 ` xfs Martin K. Petersen
2002-03-09  0:07   ` xfs Pete Popov
2002-03-10 23:04     ` xfs Liam Davies
2002-03-09  9:17 ` xfs Keith Owens
2002-03-09 18:12   ` xfs Pete Popov
2002-03-10  5:30 ` xfs Steven J. Hill

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=1015982952.5196.62.camel@zeus \
    --to=ppopov@mvista.com \
    --cc=linux-mips@oss.sgi.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