From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>
Cc: smfrench@gmail.com, linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, linux-cifs@vger.kernel.org,
Steve French <stfrench@microsoft.com>,
ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: Re: [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table
Date: Fri, 16 Jan 2026 22:30:57 +0800 [thread overview]
Message-ID: <3782f12b-b2be-42d0-a91b-eb1239548684@linux.dev> (raw)
In-Reply-To: <CA+5B0FOT_H1vO+9cfSbpFsUauQ_V1KM0GGKjp=+_K+z-SEWNeA@mail.gmail.com>
I am concerned that X macros may make the code harder to read. What do
others think?
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 1/16/26 21:48, Aurélien Aptel wrote:
> May I suggest using X macros?
> you don't need pre-processing and generation of files and you can keep
> as much metadata as you want in the macro at zero runtime cost and
> build what you need.
>
> You can have one .h file like this:
>
> #define SMB2_ERR_LIST \
> X(STATUS_WAIT_1, 0x00000000, -EIO, <whatever else>) \
> X(STATUS_WAIT_2, 0x00000001, -EIO, <whatever else>) \
> ...
>
> and then do things like:
>
> enum smb2_error {
> #define X(code, val, ...) code = cpu_to_le32(val),
> SMB2_ERR_LIST
> #undef X
> };
>
> Might have to use typed enum to get the le32 through
> https://gcc.gnu.org/onlinedocs/gcc/Enum-Extensions.html
>
> struct smb2_errno_map { le32 code; const char *name; int errno; };
> struct smb2_errno_map smb2_to_errno[] = {
> #define X(name, val, errno, ...) {cpu_to_le32(val), #name, errno},
> SMB2_ERR_LIST
> #undef X
> };
>
> Also you can use bsearch() to do log(N) lookup. But maybe the compiler
> optimizes a larger switch to the same thing already.
>
> static int cmp_smb2_err(const void *key, const void *elt)
> {
> return *(const enum smb2_error *)key - ((const struct
> smb2_errno_map *)elt)->val;
> }
>
> int smb2_err_lookup(enum smb2_error err)
> {
> struct smb2_errno_map *res = bsearch(&err, smb2_to_errno,
> ARRAY_SIZE(smb2_to_errno), sizeof(smb2_to_errno[0]), cmp_smb2_err);
> ...
> }
>
>
> (code untested)
next prev parent reply other threads:[~2026-01-16 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 7:15 [PATCH v8 0/5] smb: improve search speed of SMB2 maperror chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 1/5] cifs: Label SMB2 statuses with errors chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table chenxiaosong.chenxiaosong
2026-01-16 8:14 ` ChenXiaoSong
2026-01-16 13:48 ` Aurélien Aptel
2026-01-16 14:30 ` ChenXiaoSong [this message]
2026-01-16 14:51 ` ChenXiaoSong
2026-01-06 7:15 ` [PATCH v8 3/5] smb/client: check whether smb2_error_map_table is sorted in ascending order chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 4/5] smb/client: use bsearch() to find target in smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 5/5] smb/client: introduce KUnit test to check search result of smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06 9:34 ` [PATCH v8 0/5] smb: improve search speed of SMB2 maperror David Howells
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=3782f12b-b2be-42d0-a91b-eb1239548684@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=aurelien.aptel@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.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 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.