Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next] ice: Add low latency Tx timestamp read
Date: Mon, 25 Jul 2022 10:48:41 +0200	[thread overview]
Message-ID: <20220725084841.2082138-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20220722153610.499172-1-karol.kolacinski@intel.com>

From: Karol Kolacinski <karol.kolacinski@intel.com>
Date: Fri, 22 Jul 2022 17:36:10 +0200

(offtop below)

> E810 products can support low latency Tx timestamp register read.
> This requires usage of threaded IRQ instead of kthread to reduce the
> kthread start latency (spikes up to 20 ms).
> Add a check for the device capability and use the new method if
> supported.
> 
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
>  drivers/net/ethernet/intel/ice/ice_common.c |  4 +
>  drivers/net/ethernet/intel/ice/ice_main.c   | 32 +++++--
>  drivers/net/ethernet/intel/ice/ice_ptp.c    | 47 +++++-----
>  drivers/net/ethernet/intel/ice/ice_ptp.h    |  7 +-
>  drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 98 ++++++++++++++++++---
>  drivers/net/ethernet/intel/ice/ice_ptp_hw.h |  7 ++
>  drivers/net/ethernet/intel/ice/ice_type.h   |  2 +
>  7 files changed, 152 insertions(+), 45 deletions(-)

[...]

> diff --git a/drivers/net/ethernet/intel/ice/ice_type.h b/drivers/net/ethernet/intel/ice/ice_type.h
> index 861b64322959..920c47ddbe8d 100644
> --- a/drivers/net/ethernet/intel/ice/ice_type.h
> +++ b/drivers/net/ethernet/intel/ice/ice_type.h
> @@ -347,6 +347,7 @@ struct ice_ts_func_info {
>  #define ICE_TS_DEV_ENA_M		BIT(24)
>  #define ICE_TS_TMR0_ENA_M		BIT(25)
>  #define ICE_TS_TMR1_ENA_M		BIT(26)
> +#define ICE_TS_LL_TX_TS_READ_M		BIT(28)
>  
>  struct ice_ts_dev_info {
>  	/* Device specific info */
> @@ -359,6 +360,7 @@ struct ice_ts_dev_info {
>  	u8 ena;
>  	u8 tmr0_ena;
>  	u8 tmr1_ena;
> +	u8 ts_ll_read;

Those all are flags, what about converting them to a bitfield/bitmap
(in a separate patch)? 1 byte per bit is a waste. Even though
currently there are 6 bytes accupied (after your addition) and long
(unsigned) is of 8 bytes, more flags here will waste more and more
space.

>  };
>  
>  /* Function specific capabilities */
> -- 
> 2.34.1

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

  reply	other threads:[~2022-07-25  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 15:36 [Intel-wired-lan] [PATCH net-next] ice: Add low latency Tx timestamp read Karol Kolacinski
2022-07-25  8:48 ` Alexander Lobakin [this message]
2022-07-26 21:39 ` Tony Nguyen
2022-07-28 12:53   ` Kolacinski, Karol

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=20220725084841.2082138-1-alexandr.lobakin@intel.com \
    --to=alexandr.lobakin@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=karol.kolacinski@intel.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