netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>
Cc: Carolina Jubran <cjubran@nvidia.com>,
	Bar Shapira <bshapira@nvidia.com>,
	netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
	Paolo Abeni <pabeni@redhat.com>,
	Richard Cochran <richardcochran@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Dragos Tatulea <dtatulea@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>, Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH net-next] net/mlx5: use do_aux_work for PHC overflow checks
Date: Mon, 6 Jan 2025 16:45:22 +0200	[thread overview]
Message-ID: <837e39b7-0e95-4f6d-b2cb-8dbefa9eb696@gmail.com> (raw)
In-Reply-To: <6c9730b3-b35d-47d9-9cd6-ec2e05e4e8e5@linux.dev>



On 04/01/2025 0:25, Vadim Fedorenko wrote:
> On 22/12/2024 14:10, Dragos Tatulea wrote:
>> On Tue Dec 17, 2024 at 8:57 PM CET, Vadim Fedorenko wrote:
>>> The overflow_work is using system wq to do overflow checks and updates
>>> for PHC device timecounter, which might be overhelmed by other tasks.
>>> But there is dedicated kthread in PTP subsystem designed for such
>>> things. This patch changes the work queue to proper align with PTP
>>> subsystem and to avoid overloading system work queue.
>>> The adjfine() function acts the same way as overflow check worker,
>>> we can postpone ptp aux worker till the next overflow period after
>>> adjfine() was called.
>>>
>>> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
>>> ---
>>>   .../ethernet/mellanox/mlx5/core/lib/clock.c   | 25 +++++++++++--------
>>>   include/linux/mlx5/driver.h                   |  1 -
>>>   2 files changed, 14 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c b/ 
>>> drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>>> index 4822d01123b4..ff3780331273 100644
>>> --- a/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>>> +++ b/drivers/net/ethernet/mellanox/mlx5/core/lib/clock.c
>>> @@ -322,17 +322,16 @@ static void mlx5_pps_out(struct work_struct *work)
>>>       }
>>>   }
>>> -static void mlx5_timestamp_overflow(struct work_struct *work)
>>> +static long mlx5_timestamp_overflow(struct ptp_clock_info *ptp_info)
>>>   {
>>> -    struct delayed_work *dwork = to_delayed_work(work);
>>>       struct mlx5_core_dev *mdev;
>>>       struct mlx5_timer *timer;
>>>       struct mlx5_clock *clock;
>>>       unsigned long flags;
>>> -    timer = container_of(dwork, struct mlx5_timer, overflow_work);
>>> -    clock = container_of(timer, struct mlx5_clock, timer);
>>> +    clock = container_of(ptp_info, struct mlx5_clock, ptp_info);
>>>       mdev = container_of(clock, struct mlx5_core_dev, clock);
>>> +    timer = &clock->timer;
>>>       if (mdev->state == MLX5_DEVICE_STATE_INTERNAL_ERROR)
>>>           goto out;
>>> @@ -343,7 +342,7 @@ static void mlx5_timestamp_overflow(struct 
>>> work_struct *work)
>>>       write_sequnlock_irqrestore(&clock->lock, flags);
>>>   out:
>>> -    schedule_delayed_work(&timer->overflow_work, timer- 
>>> >overflow_period);
>>> +    return timer->overflow_period;
>>>   }
>>>   static int mlx5_ptp_settime_real_time(struct mlx5_core_dev *mdev,
>>> @@ -517,6 +516,7 @@ static int mlx5_ptp_adjfine(struct ptp_clock_info 
>>> *ptp, long scaled_ppm)
>>>       timer->cycles.mult = mult;
>>>       mlx5_update_clock_info_page(mdev);
>>>       write_sequnlock_irqrestore(&clock->lock, flags);
>>> +    ptp_schedule_worker(clock->ptp, timer->overflow_period);
>>>       return 0;
>>>   }
>>> @@ -852,6 +852,7 @@ static const struct ptp_clock_info 
>>> mlx5_ptp_clock_info = {
>>>       .settime64    = mlx5_ptp_settime,
>>>       .enable        = NULL,
>>>       .verify        = NULL,
>>> +    .do_aux_work    = mlx5_timestamp_overflow,
>>>   };
>>>   static int mlx5_query_mtpps_pin_mode(struct mlx5_core_dev *mdev, u8 
>>> pin,
>>> @@ -1052,12 +1053,12 @@ static void mlx5_init_overflow_period(struct 
>>> mlx5_clock *clock)
>>>       do_div(ns, NSEC_PER_SEC / HZ);
>>>       timer->overflow_period = ns;
>>> -    INIT_DELAYED_WORK(&timer->overflow_work, mlx5_timestamp_overflow);
>>> -    if (timer->overflow_period)
>>> -        schedule_delayed_work(&timer->overflow_work, 0);
>>> -    else
>>> +    if (!timer->overflow_period) {
>>> +        timer->overflow_period = HZ;
>>>           mlx5_core_warn(mdev,
>>> -                   "invalid overflow period, overflow_work is not 
>>> scheduled\n");
>>> +                   "invalid overflow period,"
>>> +                   "overflow_work is scheduled once per second\n");
>>> +    }
>>>       if (clock_info)
>>>           clock_info->overflow_period = timer->overflow_period;
>>> @@ -1172,6 +1173,9 @@ void mlx5_init_clock(struct mlx5_core_dev *mdev)
>>>       MLX5_NB_INIT(&clock->pps_nb, mlx5_pps_event, PPS_EVENT);
>>>       mlx5_eq_notifier_register(mdev, &clock->pps_nb);
>>> +
>>> +    if (clock->ptp)
>>> +        ptp_schedule_worker(clock->ptp, 0);
>>>   }
>>>   void mlx5_cleanup_clock(struct mlx5_core_dev *mdev)
>>> @@ -1188,7 +1192,6 @@ void mlx5_cleanup_clock(struct mlx5_core_dev 
>>> *mdev)
>>>       }
>>>       cancel_work_sync(&clock->pps_info.out_work);
>>> -    cancel_delayed_work_sync(&clock->timer.overflow_work);
>>>       if (mdev->clock_info) {
>>>           free_page((unsigned long)mdev->clock_info);
>>> diff --git a/include/linux/mlx5/driver.h b/include/linux/mlx5/driver.h
>>> index fc7e6153b73d..3ac2fc1b52cf 100644
>>> --- a/include/linux/mlx5/driver.h
>>> +++ b/include/linux/mlx5/driver.h
>>> @@ -690,7 +690,6 @@ struct mlx5_timer {
>>>       struct timecounter         tc;
>>>       u32                        nominal_c_mult;
>>>       unsigned long              overflow_period;
>>> -    struct delayed_work        overflow_work;
>>>   };
>>>   struct mlx5_clock {
>>
>> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
>>
> 
> Hi Saeed, Tariq, Leon!
> 
> We need explicit Ack-by from official mlx5 maintainer here to let this
> patch go directly to net-next. Could you please check it?
> 
> Thanks,
> Vadim
> 
> 

Hi,

Back after a long vacation.
I'll reply shortly.

Regards,
Tariq

  reply	other threads:[~2025-01-06 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 19:57 [PATCH net-next] net/mlx5: use do_aux_work for PHC overflow checks Vadim Fedorenko
2024-12-18  3:52 ` Richard Cochran
2024-12-18 10:19   ` Vadim Fedorenko
2024-12-22 14:10 ` Dragos Tatulea
2025-01-03 22:25   ` Vadim Fedorenko
2025-01-06 14:45     ` Tariq Toukan [this message]
2025-01-07  6:21 ` Tariq Toukan

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=837e39b7-0e95-4f6d-b2cb-8dbefa9eb696@gmail.com \
    --to=ttoukan.linux@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bshapira@nvidia.com \
    --cc=cjubran@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=vadim.fedorenko@linux.dev \
    /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).