From: Eric Sandeen <sandeen@sandeen.net>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: xfs@oss.sgi.com
Subject: Re: Strange XFS issue on tiny-NAS ARM NFS server
Date: Wed, 14 Mar 2007 16:21:59 -0500 [thread overview]
Message-ID: <45F86777.9030909@sandeen.net> (raw)
In-Reply-To: <EXNANE01yeKzGZuNY1S000000cb@exnane01.hq.netapp.com>
Talpey, Thomas wrote:
> Wow good memory, 3 years ago:
> <http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-March/020287.html>
>
> I'm compiling with gcc4.1.1 for arm5t big endian, patched for multiple
> arm ports (OpenEmbedded) and it still botches that code today.
> Works fine with the arithmetic decomposition in the message.
> And I never blame the compiler! ;-)
>
> Thanks!
>
> BTW, XFS gives this little machine a nice bump in NFS write
> bandwidth. Goes from ~6MB/sec to ~7MB/s. CPU limited, mainly.
Glad it worked!
So is netapp selling those now? ;-)
-Eric
next prev parent reply other threads:[~2007-03-14 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 16:11 Strange XFS issue on tiny-NAS ARM NFS server Talpey, Thomas
2007-03-14 20:32 ` Eric Sandeen
2007-03-14 21:19 ` Talpey, Thomas
2007-03-14 21:21 ` Eric Sandeen [this message]
2007-03-14 21:31 ` Talpey, Thomas
2007-03-15 11:34 ` Talpey, Thomas
2007-03-15 22:59 ` David Chinner
2007-03-16 11:30 ` Talpey, Thomas
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=45F86777.9030909@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Thomas.Talpey@netapp.com \
--cc=xfs@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 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.