From: Charles Manning <manningc2@actrix.gen.nz>
To: David Woodhouse <dwmw2@infradead.org>,
Jarkko Lavinen <jarkko.lavinen@nokia.com>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 case insensitivity
Date: Wed, 28 Jan 2004 11:49:02 +1300 [thread overview]
Message-ID: <20040127224134.9F91515D43@desire.actrix.co.nz> (raw)
In-Reply-To: <1075216726.1633.125.camel@hades.cambridge.redhat.com>
On Wednesday 28 January 2004 04:18, David Woodhouse wrote:
> > My primary concern was to estimate the cost or pain of implementing
> > file name case insensitivity and find arguments against doing it in
> > the kernel.
>
> It is fairly painful -- you have to provide your own dentry_ops for
> comparison and hashing, which mostly sorts out the evil dcache coherency
> issues we used to have with case-insensitivity.
>
> But you still have to know the character set. That was vaguely OK for
> FAT, where we had to play charset games anyway, but I _really_ don't
> want to have the JFFS2 code play with character sets and know that û is
> really the same as �, etc. And don't get me started on Ŵ and ŵ :)
>
> You really ought to be able to do this in userspace.
I agree completely with David.
I had to add case insensitivity to YAFFS for WinCE. There were enough wierd
things just to make that work. On top of that, with Linux there is all the
overhead of modifying dentry behaviour, handling renaming oddities etc. This
is non-trivial to get right.
Doing this in user space is by far the easiest.
-- Charles
next prev parent reply other threads:[~2004-01-27 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 10:06 JFFS2 case insensitivity Jarkko Lavinen
2004-01-27 11:13 ` David Woodhouse
2004-01-27 13:48 ` Jarkko Lavinen
2004-01-27 15:18 ` David Woodhouse
2004-01-27 22:49 ` Charles Manning [this message]
2004-01-28 6:13 ` David Woodhouse
2004-02-20 21:01 ` David Woodhouse
2004-01-27 13:48 ` David Woodhouse
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=20040127224134.9F91515D43@desire.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=dwmw2@infradead.org \
--cc=jarkko.lavinen@nokia.com \
--cc=linux-mtd@lists.infradead.org \
/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