From: chenxiaosong.chenxiaosong@linux.dev
To: sfrench@samba.org, smfrench@gmail.com, linkinjeon@kernel.org,
linkinjeon@samba.org
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
chenxiaosong@chenxiaosong.com,
ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: [PATCH v2 0/9] smb: improve search speed of SMB2 maperror
Date: Fri, 5 Dec 2025 12:29:48 +0800 [thread overview]
Message-ID: <20251205042958.2658496-1-chenxiaosong.chenxiaosong@linux.dev> (raw)
From: ChenXiaoSong <chenxiaosong@kylinos.cn>
Before applying this patchset, when searching for the last element of
smb2_error_map_table array and calling smb2_print_status(),
3486 comparisons are needed.
After applying this patchset, only 10 comparisons are required.
v1: https://lore.kernel.org/linux-cifs/20251204045818.2590727-1-chenxiaosong.chenxiaosong@linux.dev/
v1->v2:
- Patch #0001: update commit message: array has 1743 elements
- Split into two patches: #0003 #0004
- Patch #0009: update commit message
- Do not move smb2maperror.c to common/
ChenXiaoSong (9):
smb/client: reduce loop count in map_smb2_to_linux_error() by half
smb/client: remove unused elements from smb2_error_map_table array
smb: rename to STATUS_SMB_NO_PREAUTH_INTEGRITY_HASH_OVERLAP
smb/client: add two elements to smb2_error_map_table array
smb/client: sort smb2_error_map_table array
smb/client: use bsearch() to find target status code
smb/client: introduce smb2_get_err_map()
smb/client: introduce smb2maperror KUnit tests
smb/server: rename include guard in smb_common.h
fs/smb/Kconfig | 13 +++
fs/smb/client/cifsfs.c | 2 +
fs/smb/client/smb2maperror.c | 159 ++++++++++++++++++++++++++++-------
fs/smb/client/smb2proto.h | 1 +
fs/smb/common/smb2status.h | 5 +-
fs/smb/server/smb2pdu.c | 2 +-
fs/smb/server/smb_common.h | 6 +-
7 files changed, 150 insertions(+), 38 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-05 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 4:29 chenxiaosong.chenxiaosong [this message]
2025-12-05 4:29 ` [PATCH v2 1/9] smb/client: reduce loop count in map_smb2_to_linux_error() by half chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 2/9] smb/client: remove unused elements from smb2_error_map_table array chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 3/9] smb: rename to STATUS_SMB_NO_PREAUTH_INTEGRITY_HASH_OVERLAP chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 4/9] smb/client: add two elements to smb2_error_map_table array chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 5/9] smb/client: sort " chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 6/9] smb/client: use bsearch() to find target status code chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 7/9] smb/client: introduce smb2_get_err_map() chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 8/9] smb/client: introduce smb2maperror KUnit tests chenxiaosong.chenxiaosong
2025-12-05 4:29 ` [PATCH v2 9/9] smb/server: rename include guard in smb_common.h chenxiaosong.chenxiaosong
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=20251205042958.2658496-1-chenxiaosong.chenxiaosong@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=chenxiaosong@chenxiaosong.com \
--cc=chenxiaosong@kylinos.cn \
--cc=linkinjeon@kernel.org \
--cc=linkinjeon@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
/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
all inboxes | Powered by JetHome®