> Note that my interest in speeding up msdos file name lookups is very close
> to zero, which is why I don't care if msdos filenames cannot use the
> dcache very efficiently. So I'm not interested in 1% vs 50%, if that 50%
> is in a filesystem that I don't consider to be very performance-critical
> in the first place.
Thats ok - the best way to accelerate msdos-fs would be to copy its
contents to ext2.
> Note that something I _could_ add to the filesystem is a simple per-dentry
> flag that indicates case-sensitivity. That would not require us to call
> out to the low-level filesystem (with the problems wrt SMP that that
> implies), because we could do it all within the trusted VFS layer (all the
> operations it needs to do are "fast").
If it would mean that I could not be able to cp
really.ugly.and.big.filename /dosc? That would be bad think, as it
would break _me_. Emagine you want to copy 100 such files from ext2 to
msdosfs. This _should_ be possible, or you've just made msdos fs
unusable for me.
> The thing that makes me think that having the VFS layer handle
> case-insenstitivity (but nothing else) is a good idea is that it can
> potentially be useful even for things like ext2fs. Imagine having not to
> worry about case in DOSEMU or Wine, but instead doing
>
> int fd = open("/dosc/windows/windows.ini", O_NOCASE |
> O_RDONLY);
_I_ think, that dosemu should be well-behaved and doing its
lower-casing auto-magically. No need dto support it in kernel.
And btw think about dos's disk named 'BigDosC' while having file
bigdosc in root directory? Seems like mess to me.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).