Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
	jesse.brandeburg@intel.com,
	Michal Michalik <michal.michalik@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Schedule service task in IRQ top half
Date: Fri, 24 Nov 2023 12:46:33 +0100	[thread overview]
Message-ID: <6a45ca42-c23f-21f0-ccbf-7ea6bb5bd408@intel.com> (raw)
In-Reply-To: <20231124114155.251360-1-karol.kolacinski@intel.com>

On 11/24/23 12:41, Karol Kolacinski wrote:
> Schedule service task and EXTTS in the top half to avoid bottom half
> scheduling if possible, which significantly reduces timestamping delay.
> 
> Co-developed-by: Michal Michalik <michal.michalik@intel.com>
> Signed-off-by: Michal Michalik <michal.michalik@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
>   drivers/net/ethernet/intel/ice/ice.h      |  1 -
>   drivers/net/ethernet/intel/ice/ice_main.c | 18 ++++++++++--------
>   2 files changed, 10 insertions(+), 9 deletions(-)
> 

Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2023-11-24 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 11:41 [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Schedule service task in IRQ top half Karol Kolacinski
2023-11-24 11:41 ` [Intel-wired-lan] [PATCH iwl-next 2/2] ice: Enable SW interrupt from FW for LL TS Karol Kolacinski
2023-11-24 11:46   ` Przemek Kitszel
2023-11-24 11:46 ` Przemek Kitszel [this message]
2023-11-27 16:46 ` [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Schedule service task in IRQ top half Simon Horman

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=6a45ca42-c23f-21f0-ccbf-7ea6bb5bd408@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=karol.kolacinski@intel.com \
    --cc=michal.michalik@intel.com \
    --cc=netdev@vger.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