From: "Theodore Ts'o" <tytso@mit.edu>
To: Matthew Wilcox <willy@infradead.org>
Cc: HAN Yuwei <hrx@bupt.moe>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Questions about Unicode Normalization Form
Date: Mon, 8 Apr 2024 10:15:04 -0400 [thread overview]
Message-ID: <20240408141504.GA122316@mit.edu> (raw)
In-Reply-To: <ZhNk78RE2Bocs9ap@casper.infradead.org>
On Mon, Apr 08, 2024 at 04:30:55AM +0100, Matthew Wilcox wrote:
> As I understand it, an important usecase for the casefold feature is
> running Windows games under WINE. I don't do this myself (sgt-puzzles
> is more my speed), but there's a pretty important market for this.
> Wasn't this why Gabriel was funded to work on it (eg commit b886ee3e778e)?
> Or was that the Android usecase?
Good point. Your history is correct; the other use case, which Gabriel
was funded to do the work for, was for Steam for Linux, which uses a
fork of Wine called Stream Play.
The other potential use case for casefold is that it would accelarate
Samba servers, which will first try to do a lookup on the filename but
if it gets ENOENT, has to do an O(1) readdir search to see if there is
a case insensitive match to the given lookup. I haven't heard of
anyone who has actually configured their CIFS server to do this, but
it should work.
- Ted
prev parent reply other threads:[~2024-04-08 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 9:54 Questions about Unicode Normalization Form HAN Yuwei
2024-04-06 13:26 ` James Bottomley
2024-04-06 15:15 ` HAN Yuwei
2024-04-08 1:39 ` Theodore Ts'o
2024-04-08 1:57 ` HAN Yuwei
2024-04-08 3:30 ` Matthew Wilcox
2024-04-08 14:15 ` Theodore Ts'o [this message]
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=20240408141504.GA122316@mit.edu \
--to=tytso@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hrx@bupt.moe \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@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 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.