All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net v1] ice: Create a separate kthread to handle ptp extts work
Date: Tue, 1 Nov 2022 13:54:03 -0700	[thread overview]
Message-ID: <ee73169c-0060-e997-8661-c0e76cff12ff@intel.com> (raw)
In-Reply-To: <20221031071430.5998-1-anatolii.gerasymenko@intel.com>

On 10/31/2022 12:14 AM, Anatolii Gerasymenko wrote:
> ice_ptp_extts_work() and ice_ptp_periodic_work() are both scheduled on
> the same kthread_worker pf.ptp.kworker. But, ice_ptp_periodic_work()
> sends messages to ADQ and waits for responses. This causes

Is this supposed to be AQ (not ADQ)?

> ice_ptp_extts_work() to be blocked while waiting to be scheduled. This
> causes problems with the reading of the incoming signal timestamps,
> which disrupts a 100 Hz signal.
> 
> Create an additional kthread_worker pf.ptp.kworker_extts to service only
> ice_ptp_extts_work() as soon as possible.
> 
> Fixes: 77a781155a65 ("ice: enable receive hardware timestamping")
> Signed-off-by: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-11-01 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  7:14 [Intel-wired-lan] [PATCH net v1] ice: Create a separate kthread to handle ptp extts work Anatolii Gerasymenko
2022-11-01 20:54 ` Tony Nguyen [this message]
2022-11-02  8:03   ` Anatolii Gerasymenko

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=ee73169c-0060-e997-8661-c0e76cff12ff@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=anatolii.gerasymenko@intel.com \
    --cc=intel-wired-lan@lists.osuosl.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 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.