| To: | Christoph Litauer <litauer@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: rfc: kill ino64 mount option |
| From: | Mark Goodwin <markgw@xxxxxxx> |
| Date: | Wed, 02 Jul 2008 00:12:43 +1000 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4869E5A4.4020900@xxxxxxxxxxxxxx> |
| Organization: | SGI Engineering |
| References: | <20080627153928.GA31384@xxxxxx> <20080628000914.GE29319@disturbed> <486589E7.9010705@xxxxxxx> <4869E5A4.4020900@xxxxxxxxxxxxxx> |
| Reply-to: | markgw@xxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.14 (Windows/20080421) |
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 ofinodes, I am very interested in this "incode32+". can you please post some details of the problems you're seeing? 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. Thanks -- Mark |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [dm-devel] Re: [PATCH 3/3] Add timeout feature, Alasdair G Kergon |
|---|---|
| Next by Date: | Re: rfc: kill ino64 mount option, Christoph Litauer |
| Previous by Thread: | Re: rfc: kill ino64 mount option, Christoph Litauer |
| Next by Thread: | Re: rfc: kill ino64 mount option, Christoph Litauer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |