From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: zyjzyj2000@gmail.com, jgg@ziepe.ca, leon@kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Remove unused rxe_run_task
Date: Sat, 19 Apr 2025 08:44:23 +0200 [thread overview]
Message-ID: <7ca8fd94-da46-40ad-8ced-31fe033ee100@linux.dev> (raw)
In-Reply-To: <aALsrZxAqhwxDD7d@gallifrey>
在 2025/4/19 2:22, Dr. David Alan Gilbert 写道:
>
> Hi,
>
>> Thanks a lot. Please add the Fixes tags.
>> Fixes: 23bc06af547f ("RDMA/rxe: Don't call direct between tasks")
>
> Thanks for the review; I've tended to avoid the fixes tag because
> people use 'Fixes' to automatically pull in patches to stable or
> downstream kernels, and there is no need for them to do that for
> a cleanup patch.
>
>> And in the following comments, the function rxe_run_task is still mentioned.
>> "
>> 86 /* do_task is a wrapper for the three tasks (requester,
>> 87 * completer, responder) and calls them in a loop until
>> 88 * they return a non-zero value. It is called either
>> 89 * directly by rxe_run_task or indirectly if rxe_sched_task
>> 90 * schedules the task. They must call __reserve_if_idle to
>> 91 * move the task to busy before calling or scheduling.
>> 92 * The task can also be moved to drained or invalid
>> 93 * by calls to rxe_cleanup_task or rxe_disable_task.
>> 94 * In that case tasks which get here are not executed but
>> 95 * just flushed. The tasks are designed to look to see if
>> 96 * there is work to do and then do part of it before returning
>> 97 * here with a return value of zero until all the work
>> 98 * has been consumed then it returns a non-zero value.
>> 99 * The number of times the task can be run is limited by
>> 100 * max iterations so one task cannot hold the cpu forever.
>> 101 * If the limit is hit and work remains the task is rescheduled.
>> 102 */
>> "
>> Not sure if you like to modify the above comments to remove rxe_run_task or
>> not.
>
> Would it be correct to just reword:
>> 88 * It is called either
>> 89 * directly by rxe_run_task or indirectly if rxe_sched_task
>> 90 * schedules the task.
>
> to:
> It is called indirectly when rxe_sched_task schedules the task.
I am fine with it. Thanks a lot.
Zhu Yanjun
>
>> Except the above, I am fine with this commit.
>
> Thanks!
>
>> Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> Dave
>
next prev parent reply other threads:[~2025-04-19 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 16:59 [PATCH] RDMA/rxe: Remove unused rxe_run_task linux
2025-04-18 19:08 ` Zhu Yanjun
2025-04-19 0:22 ` Dr. David Alan Gilbert
2025-04-19 6:44 ` Zhu Yanjun [this message]
2025-04-19 13:28 ` Dr. David Alan Gilbert
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=7ca8fd94-da46-40ad-8ced-31fe033ee100@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@treblig.org \
--cc=zyjzyj2000@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