From: Deanan <delusion@delusion.com>
To: xfs@oss.sgi.com
Subject: inode64 workaround
Date: Wed, 29 Nov 2006 15:43:04 -0800 [thread overview]
Message-ID: <456E1B08.7090802@delusion.com> (raw)
In-Reply-To: <1164838985.4992.30.camel@edge>
Hi,
I've got some systems that I can't change the kernel on (external
vendor) that
are 32bit but I'm running into the performance problem that is fixed by
using
inode64. Is there any known way of working around the problem on a 32bit
kernel?
In our case, the problem occurs as soon as you start to delete files and
write new ones.
Cheers,
Deanan
next prev parent reply other threads:[~2006-11-30 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:27 [PATCH 2/2]xfs_io man page Utako Kusaka
2006-11-29 22:23 ` Nathan Scott
2006-11-29 23:43 ` Deanan [this message]
2006-11-30 0:47 ` inode64 workaround David Chatterton
2006-11-30 0:59 ` Deanan
2006-11-30 1:15 ` David Chatterton
2006-11-30 1:37 ` Deanan
2006-11-30 5:11 ` Eric Sandeen
2006-11-30 20:33 ` Deanan
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=456E1B08.7090802@delusion.com \
--to=delusion@delusion.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox