From: Leon Romanovsky <leon@kernel.org>
To: Anand Khoje <anand.a.khoje@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
rama.nichanamatlu@oracle.com, manjunath.b.patil@oracle.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] RDMA/mlx5: Release CPU for other processes in mlx5_free_cmd_msg()
Date: Fri, 31 May 2024 13:00:00 +0300 [thread overview]
Message-ID: <20240531100000.GG3884@unreal> (raw)
In-Reply-To: <f6d81694-c321-470e-8b53-dcdf24d67c9b@oracle.com>
On Fri, May 31, 2024 at 10:21:39AM +0530, Anand Khoje wrote:
>
> On 5/30/24 22:44, Leon Romanovsky wrote:
> > On Wed, May 22, 2024 at 09:02:56AM +0530, Anand Khoje wrote:
> > > In non FLR context, at times CX-5 requests release of ~8 million device pages.
> > > This needs humongous number of cmd mailboxes, which to be released once
> > > the pages are reclaimed. Release of humongous number of cmd mailboxes
> > > consuming cpu time running into many secs, with non preemptable kernels
> > > is leading to critical process starving on that cpu’s RQ. To alleviate
> > > this, this patch relinquishes cpu periodically but conditionally.
> > >
> > > Orabug: 36275016
> > >
> > > Signed-off-by: Anand Khoje <anand.a.khoje@oracle.com>
> > > ---
> > > drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> > > diff --git a/drivers/net/ethernet/mellanox/mlx5/core/cmd.c b/drivers/net/ethernet/mellanox/mlx5/core/cmd.c
> > > index 9c21bce..9fbf25d 100644
> > > --- a/drivers/net/ethernet/mellanox/mlx5/core/cmd.c
> > > +++ b/drivers/net/ethernet/mellanox/mlx5/core/cmd.c
> > > @@ -1336,16 +1336,23 @@ static struct mlx5_cmd_msg *mlx5_alloc_cmd_msg(struct mlx5_core_dev *dev,
> > > return ERR_PTR(err);
> > > }
> > > +#define RESCHED_MSEC 2
> > > static void mlx5_free_cmd_msg(struct mlx5_core_dev *dev,
> > > struct mlx5_cmd_msg *msg)
> > > {
> > > struct mlx5_cmd_mailbox *head = msg->next;
> > > struct mlx5_cmd_mailbox *next;
> > > + unsigned long start_time = jiffies;
> > > while (head) {
> > > next = head->next;
> > > free_cmd_box(dev, head);
> > Did you consider to make this function asynchronous and parallel?
> >
> > Thanks
>
> Hi Leon,
>
> Thanks for reviewing this patch.
>
> Here, all page related methods give_pages/reclaim_pages/release_all_pages
> are executed in a worker thread through pages_work_handler().
>
> Doesn't that mean it is already asynchronous?
You didn't provide any performance data, so I can't say if it is related to work_handlers.
For example, we can be in this loop when we call to mlx5_cmd_disable()
and it will cause to synchronous calls to dma_pool_free() which holds
the spinlock.
Also pages_work_handler() runs through single threaded workqueue, it is
not asynchronous.
>
> When the worker thread, in this case it is processing reclaim_pages(), is
> taking a long time - it is starving other processes on the processor that it
> is running on. Oracle UEK being a non-preemptible kernel, these other
> processes that are getting starved do not get CPU until the worker
> relinquishes the CPU. This applies to even processes that are time critical
> and high priority. These processes when starved of CPU for a long time,
> trigger a kernel panic.
Please add kernel panic and perf data to your commit message.
>
> Hence, this patch implements a time based relinquish of CPU using
> cond_resched().
>
> Shay Dori, had a suggestion to tune the time (which we have made 2 msec), to
> reduce too frequent context switching and find a balance in processing of
> these mailbox objects. I am presently running some tests on the basis of
> this suggestion.
You will have better results if you parallel page release.
Thanks
>
> Thanks,
>
> Anand
>
> > > head = next;
> > > + if (time_after(jiffies, start_time + msecs_to_jiffies(RESCHED_MSEC))) {
> > > + mlx5_core_warn_rl(dev, "Spent more than %d msecs, yielding CPU\n", RESCHED_MSEC);
> > > + cond_resched();
> > > + start_time = jiffies;
> > > + }
> > > }
> > > kfree(msg);
> > > }
> > > --
> > > 1.8.3.1
> > >
> > >
prev parent reply other threads:[~2024-05-31 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 3:32 [PATCH 0/1] RDMA/mlx5: Release CPU for other processes in mlx5_free_cmd_msg() Anand Khoje
2024-05-22 3:32 ` [PATCH 1/1] " Anand Khoje
2024-05-26 15:23 ` Shay Drori
2024-05-29 12:01 ` Anand Khoje
2024-05-30 17:14 ` Leon Romanovsky
2024-05-31 4:51 ` Anand Khoje
2024-05-31 10:00 ` Leon Romanovsky [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=20240531100000.GG3884@unreal \
--to=leon@kernel.org \
--cc=anand.a.khoje@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rama.nichanamatlu@oracle.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.