From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: NeilBrown <neilb@suse.de>
Cc: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>, Tom Talpey <tom@talpey.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-debuggers@vger.kernel.org, Dai Ngo <Dai.Ngo@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 1/1] SUNRPC: convert RPC_TASK_* constants to enum
Date: Fri, 16 Aug 2024 16:12:35 -0700 [thread overview]
Message-ID: <87ttfkoye4.fsf@oracle.com> (raw)
In-Reply-To: <172384934590.6062.4979843897031230836@noble.neil.brown.name>
"NeilBrown" <neilb@suse.de> writes:
> On Sat, 17 Aug 2024, Stephen Brennan wrote:
>> The RPC_TASK_* constants are defined as macros, which means that most
>> kernel builds will not contain their definitions in the debuginfo.
>> However, it's quite useful for debuggers to be able to view the task
>> state constant and interpret it correctly. Conversion to an enum will
>> ensure the constants are present in debuginfo and can be interpreted by
>> debuggers without needing to hard-code them and track their changes.
>>
>> Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
>> ---
>> include/linux/sunrpc/sched.h | 16 +++++++++-------
>> 1 file changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/include/linux/sunrpc/sched.h b/include/linux/sunrpc/sched.h
>> index 0c77ba488bbae..177220524eb5d 100644
>> --- a/include/linux/sunrpc/sched.h
>> +++ b/include/linux/sunrpc/sched.h
>> @@ -151,13 +151,15 @@ struct rpc_task_setup {
>> #define RPC_WAS_SENT(t) ((t)->tk_flags & RPC_TASK_SENT)
>> #define RPC_IS_MOVEABLE(t) ((t)->tk_flags & RPC_TASK_MOVEABLE)
>>
>> -#define RPC_TASK_RUNNING 0
>> -#define RPC_TASK_QUEUED 1
>> -#define RPC_TASK_ACTIVE 2
>> -#define RPC_TASK_NEED_XMIT 3
>> -#define RPC_TASK_NEED_RECV 4
>> -#define RPC_TASK_MSG_PIN_WAIT 5
>> -#define RPC_TASK_SIGNALLED 6
>> +enum {
>> + RPC_TASK_RUNNING = 0,
>> + RPC_TASK_QUEUED = 1,
>> + RPC_TASK_ACTIVE = 2,
>> + RPC_TASK_NEED_XMIT = 3,
>> + RPC_TASK_NEED_RECV = 4,
>> + RPC_TASK_MSG_PIN_WAIT = 5,
>> + RPC_TASK_SIGNALLED = 6,
>> +};
>
> I am strongly in favour of converting these #defines to an enum, but
> having the explicit assignments in the enum is pure noise adding no
> value at all.
I agree, I only included it in case reviewers would prefer to be able to
see the values, as they were with the #defines. But I think it's common
knowledge that enums start at 0 and increment by 1.
> Would you consider resubmiting as a simple enum that uses the default
> values?
Definitely!
Thanks,
Stephen
prev parent reply other threads:[~2024-08-16 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 22:05 [PATCH 0/1] SUNRPC: convert RPC_TASK_* constants to enum Stephen Brennan
2024-08-16 22:06 ` [PATCH 1/1] " Stephen Brennan
2024-08-16 23:02 ` NeilBrown
2024-08-16 23:12 ` Stephen Brennan [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=87ttfkoye4.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.com \
--cc=trondmy@kernel.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 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).