All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Litauer <litauer@uni-koblenz.de>
To: markgw@sgi.com
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: rfc: kill ino64 mount option
Date: Tue, 01 Jul 2008 16:45:07 +0200	[thread overview]
Message-ID: <486A42F3.3090207@uni-koblenz.de> (raw)
In-Reply-To: <486A3B5B.20402@sgi.com>

Mark Goodwin schrieb:
> 
> 
> Christoph Litauer wrote:
>> Mark Goodwin schrieb:
>> ..
>>> We have a design proposal known as "inode32+" that essentially removes
>>> the direct mapping between inode number and disk offset. This will
>>> provide all the layout and performance benefits of ino64 without the
>>> interop issues.  Until inode32+ is available, we need to keep ino64.
>>
>> Hi,
>>
>> as I have massive performance problems using xfs with millions of
>> inodes, I am very interested in this "incode32+". 
> 
> can you please post some details of the problems you're seeing?

Please see thread "Performance problems with millions of inodes". If you 
don't have it anymore, I can send it to you.

> 
>> My server is a 32 bit machine, so I am not able to use inode64.
>> Is it available?
> 
> inode32+ is only a design at the moment. An implementation is several
> months away. Until then, you'll have to update your server to 64bit.

This is, sadly, not an option at the moment ...

-- 
Regards
Christoph
________________________________________________________________________
Christoph Litauer                  litauer@uni-koblenz.de
Uni Koblenz, Computing Center,     http://www.uni-koblenz.de/~litauer
Postfach 201602, 56016 Koblenz     Fon: +49 261 287-1311, Fax: -100 1311
PGP-Fingerprint: F39C E314 2650 650D 8092 9514 3A56 FBD8 79E3 27B2

  reply	other threads:[~2008-07-01 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 15:39 rfc: kill ino64 mount option Christoph Hellwig
2008-06-28  0:09 ` Dave Chinner
2008-06-28  0:46   ` Mark Goodwin
2008-06-28  4:31     ` Eric Sandeen
2008-06-28 15:25       ` Christoph Hellwig
2008-06-28 19:52         ` Eric Sandeen
2008-07-01  8:07     ` Christoph Litauer
2008-07-01 14:12       ` Mark Goodwin
2008-07-01 14:45         ` Christoph Litauer [this message]
2008-06-28 15:23   ` Christoph Hellwig
2008-06-29 23:13     ` Nathan Scott

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=486A42F3.3090207@uni-koblenz.de \
    --to=litauer@uni-koblenz.de \
    --cc=hch@lst.de \
    --cc=markgw@sgi.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.