| To: | "Christoph Hellwig" <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 0/7] XFS: case-insensitive lookup and Unicode support |
| From: | "Barry Naujok" <bnaujok@xxxxxxx> |
| Date: | Wed, 09 Apr 2008 11:53:20 +1000 |
| Cc: | xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20080408114513.GA31734@xxxxxxxxxxxxx> |
| Organization: | SGI |
| References: | <20080402062508.017738664@xxxxxxxxxxxxxxxxxxxxxxx> <20080408114513.GA31734@xxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Opera Mail/9.24 (Win32) |
On Tue, 08 Apr 2008 21:45:13 +1000, Christoph Hellwig <hch@xxxxxxxxxxxxx>
wrote:
btw, a little comment on how to proceed. After your xfs_name patch it would be good to get the nameops and leafn cleanup in as almost independent cleanups and then the ascii only CI but already using the complex and correct lookup method. I think unicocde will take a bit longer to sort out and getting the simpler bit in first would be helpful. Yep, that is how I was proceeding when working on the return name patch with the xfs_vn_ci_lookup code. So, it will be: 1 xfs_name 2 leafn refactor 3 nameops 4 ascii ci 5 unicode ci 6 nls With NLS, it would be very nice if the Linux VFS or some layer above always pushed UTF-8 strings down rather than handling it in the filesystems that require it (there are about half a dozen at least that I'm aware of). Barry. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: inconsistent xfs log record, Michael Nishimoto |
|---|---|
| Next by Date: | Re: Lost+found, Barry Naujok |
| Previous by Thread: | Re: [PATCH 0/7] XFS: case-insensitive lookup and Unicode support, Christoph Hellwig |
| Next by Thread: | xfs_check running out of memory, Fong Vang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |