linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: ebiggers@kernel.org, viro@zeniv.linux.org.uk,
	torvalds@linux-foundation.org
Cc: tytso@mit.edu, linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
	Gabriel Krisman Bertazi <krisman@suse.de>
Subject: [PATCH v3 0/2] Try exact-match comparison ahead of case-insensitive match
Date: Fri, 19 Jan 2024 17:25:41 -0300	[thread overview]
Message-ID: <20240119202544.19434-1-krisman@suse.de> (raw)

Linus, Al, Eric,

This small series implement the exact-match comparison ahead of the
case-insensitive comparison as suggested by Linus.  The first patch only
exposes dentry_string_cmp in a header file so we can use it instead of
memcmp and the second actually do the optimization in the
case-insensitive comparison code.

Gabriel Krisman Bertazi (2):
  dcache: Expose dentry_string_cmp outside of dcache
  libfs: Attempt exact-match comparison first during casefold lookup

 fs/dcache.c            | 53 ------------------------------------------
 fs/libfs.c             | 39 +++++++++++++++++--------------
 include/linux/dcache.h | 53 ++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 75 insertions(+), 70 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-01-19 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 20:25 Gabriel Krisman Bertazi [this message]
2024-01-19 20:25 ` [PATCH v3 1/2] dcache: Expose dentry_string_cmp outside of dcache Gabriel Krisman Bertazi
2024-01-19 20:48   ` Linus Torvalds
2024-01-21 16:34     ` Gabriel Krisman Bertazi
2024-01-21 19:09       ` Linus Torvalds
2024-01-24 18:13         ` [PATCH v4] libfs: Attempt exact-match comparison first during casefolded lookup Gabriel Krisman Bertazi
2024-01-24 18:42           ` Linus Torvalds
2024-01-24 22:44             ` Eric Biggers
2024-01-19 20:25 ` [PATCH v3 2/2] libfs: Attempt exact-match comparison first during casefold lookup Gabriel Krisman Bertazi

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=20240119202544.19434-1-krisman@suse.de \
    --to=krisman@suse.de \
    --cc=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).