All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: <bpf@vger.kernel.org>, Stanislav Fomichev <sdf@google.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"Martin KaFai Lau" <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Alexander Lobakin <alexandr.lobakin@intel.com>,
	"Magnus Karlsson" <magnus.karlsson@gmail.com>,
	Maryam Tahhan <mtahhan@redhat.com>, <xdp-hints@xdp-project.net>,
	<netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND bpf-next 02/15] ice: make RX HW timestamp reading code more reusable
Date: Mon, 22 May 2023 17:07:33 +0200	[thread overview]
Message-ID: <ZGuFNesdPS5ijl/R@lincoln> (raw)
In-Reply-To: <ac1895cc-a7b0-e40c-7dfc-8ab301f39893@intel.com>

On Fri, May 19, 2023 at 06:52:13PM +0200, Alexander Lobakin wrote:
> From: Larysa Zaremba <larysa.zaremba@intel.com>
> Date: Fri, 12 May 2023 17:25:54 +0200
> 
> > Previously, we only needed RX HW timestamp in skb path,
> > hence all related code was written with skb in mind.
> > But with the addition of XDP hints via kfuncs to the ice driver,
> > the same logic will be needed in .xmo_() callbacks.
> 
> [...]
> 
> > @@ -2176,9 +2174,8 @@ ice_ptp_rx_hwtstamp(struct ice_rx_ring *rx_ring,
> >  	ts_high = le32_to_cpu(rx_desc->wb.flex_ts.ts_high);
> >  	ts_ns = ice_ptp_extend_32b_ts(cached_time, ts_high);
> >  
> > -	hwtstamps = skb_hwtstamps(skb);
> > -	memset(hwtstamps, 0, sizeof(*hwtstamps));
> > -	hwtstamps->hwtstamp = ns_to_ktime(ts_ns);
> > +	*dst = ts_ns;
> > +	return true;
> 
> Can't we use the same I wrote in the prev. comment, i.e. return 0 or
> timestamp? I don't think ts == 0 is valid.
>

Agreed with this in the answer to the previous email :)
 
> >  }
> >  
> >  /**
> 
> [...]
> 
> > + * The driver receives a notification in the receive descriptor with timestamp.
> > + * The timestamp is in ns, so we must convert the result first.
> > + */
> > +static void
> > +ice_ptp_rx_hwts_to_skb(struct ice_rx_ring *rx_ring,
> > +		       union ice_32b_rx_flex_desc *rx_desc,
> > +		       struct sk_buff *skb)
> > +{
> > +	struct skb_shared_hwtstamps *hwtstamps;
> > +	u64 ts_ns;
> > +
> > +	if (!ice_ptp_copy_rx_hwts_from_desc(rx_ring, rx_desc, &ts_ns))
> > +		return;
> > +
> > +	hwtstamps = skb_hwtstamps(skb);
> > +	memset(hwtstamps, 0, sizeof(*hwtstamps));
> > +	hwtstamps->hwtstamp = ns_to_ktime(ts_ns);
> 
> Ok, my optimizations aren't in this series :D
> If you look at the hwtimestamps in skb, you'll see all that can be
> minimized to just:
> 
> 	*skb_hwtstamps(skb) = (struct skb_shared_hwtstamps){
> 		.hwtstamp	= ns_to_ktime(ts_ns),
> 	};
> 
> Compiler will probably do its job, but I wouldn't always rely on it.
> Sometimes it's even able to not expand memset(8 bytes) to *(u64 *) = 0.

Ok, will fix.

> 
> > +}
> > +
> >  /**
> >   * ice_process_skb_fields - Populate skb header fields from Rx descriptor
> >   * @rx_ring: Rx descriptor ring packet is being transacted on
> > @@ -210,7 +235,7 @@ ice_process_skb_fields(struct ice_rx_ring *rx_ring,
> >  	ice_rx_csum(rx_ring, skb, rx_desc, ptype);
> >  
> >  	if (rx_ring->ptp_rx)
> > -		ice_ptp_rx_hwtstamp(rx_ring, rx_desc, skb);
> > +		ice_ptp_rx_hwts_to_skb(rx_ring, rx_desc, skb);
> >  }
> >  
> >  /**
> 
> Thanks,
> Olek

WARNING: multiple messages have this Message-ID (diff)
From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Stanislav Fomichev <sdf@google.com>,
	Maryam Tahhan <mtahhan@redhat.com>,
	xdp-hints@xdp-project.net, Daniel Borkmann <daniel@iogearbox.net>,
	John Fastabend <john.fastabend@gmail.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Yonghong Song <yhs@fb.com>, KP Singh <kpsingh@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Olsa <jolsa@kernel.org>,
	bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@linux.dev>
Subject: Re: [Intel-wired-lan] [PATCH RESEND bpf-next 02/15] ice: make RX HW timestamp reading code more reusable
Date: Mon, 22 May 2023 17:07:33 +0200	[thread overview]
Message-ID: <ZGuFNesdPS5ijl/R@lincoln> (raw)
In-Reply-To: <ac1895cc-a7b0-e40c-7dfc-8ab301f39893@intel.com>

On Fri, May 19, 2023 at 06:52:13PM +0200, Alexander Lobakin wrote:
> From: Larysa Zaremba <larysa.zaremba@intel.com>
> Date: Fri, 12 May 2023 17:25:54 +0200
> 
> > Previously, we only needed RX HW timestamp in skb path,
> > hence all related code was written with skb in mind.
> > But with the addition of XDP hints via kfuncs to the ice driver,
> > the same logic will be needed in .xmo_() callbacks.
> 
> [...]
> 
> > @@ -2176,9 +2174,8 @@ ice_ptp_rx_hwtstamp(struct ice_rx_ring *rx_ring,
> >  	ts_high = le32_to_cpu(rx_desc->wb.flex_ts.ts_high);
> >  	ts_ns = ice_ptp_extend_32b_ts(cached_time, ts_high);
> >  
> > -	hwtstamps = skb_hwtstamps(skb);
> > -	memset(hwtstamps, 0, sizeof(*hwtstamps));
> > -	hwtstamps->hwtstamp = ns_to_ktime(ts_ns);
> > +	*dst = ts_ns;
> > +	return true;
> 
> Can't we use the same I wrote in the prev. comment, i.e. return 0 or
> timestamp? I don't think ts == 0 is valid.
>

Agreed with this in the answer to the previous email :)
 
> >  }
> >  
> >  /**
> 
> [...]
> 
> > + * The driver receives a notification in the receive descriptor with timestamp.
> > + * The timestamp is in ns, so we must convert the result first.
> > + */
> > +static void
> > +ice_ptp_rx_hwts_to_skb(struct ice_rx_ring *rx_ring,
> > +		       union ice_32b_rx_flex_desc *rx_desc,
> > +		       struct sk_buff *skb)
> > +{
> > +	struct skb_shared_hwtstamps *hwtstamps;
> > +	u64 ts_ns;
> > +
> > +	if (!ice_ptp_copy_rx_hwts_from_desc(rx_ring, rx_desc, &ts_ns))
> > +		return;
> > +
> > +	hwtstamps = skb_hwtstamps(skb);
> > +	memset(hwtstamps, 0, sizeof(*hwtstamps));
> > +	hwtstamps->hwtstamp = ns_to_ktime(ts_ns);
> 
> Ok, my optimizations aren't in this series :D
> If you look at the hwtimestamps in skb, you'll see all that can be
> minimized to just:
> 
> 	*skb_hwtstamps(skb) = (struct skb_shared_hwtstamps){
> 		.hwtstamp	= ns_to_ktime(ts_ns),
> 	};
> 
> Compiler will probably do its job, but I wouldn't always rely on it.
> Sometimes it's even able to not expand memset(8 bytes) to *(u64 *) = 0.

Ok, will fix.

> 
> > +}
> > +
> >  /**
> >   * ice_process_skb_fields - Populate skb header fields from Rx descriptor
> >   * @rx_ring: Rx descriptor ring packet is being transacted on
> > @@ -210,7 +235,7 @@ ice_process_skb_fields(struct ice_rx_ring *rx_ring,
> >  	ice_rx_csum(rx_ring, skb, rx_desc, ptype);
> >  
> >  	if (rx_ring->ptp_rx)
> > -		ice_ptp_rx_hwtstamp(rx_ring, rx_desc, skb);
> > +		ice_ptp_rx_hwts_to_skb(rx_ring, rx_desc, skb);
> >  }
> >  
> >  /**
> 
> Thanks,
> Olek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-05-22 15:10 UTC|newest]

Thread overview: 108+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 15:25 [PATCH RESEND bpf-next 00/15] new kfunc XDP hints and ice implementation Larysa Zaremba
2023-05-12 15:25 ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:25 ` [PATCH RESEND bpf-next 01/15] ice: make RX hash reading code more reusable Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-19 16:46   ` Alexander Lobakin
2023-05-19 16:46     ` [Intel-wired-lan] " Alexander Lobakin
2023-05-22 15:03     ` Larysa Zaremba
2023-05-22 15:03       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-22 15:36       ` Alexander Lobakin
2023-05-22 15:36         ` [Intel-wired-lan] " Alexander Lobakin
2023-05-12 15:25 ` [PATCH RESEND bpf-next 02/15] ice: make RX HW timestamp " Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-19 16:52   ` Alexander Lobakin
2023-05-19 16:52     ` [Intel-wired-lan] " Alexander Lobakin
2023-05-22 15:07     ` Larysa Zaremba [this message]
2023-05-22 15:07       ` Larysa Zaremba
2023-05-12 15:25 ` [PATCH RESEND bpf-next 03/15] ice: make RX checksum checking " Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-22 15:51   ` Alexander Lobakin
2023-05-22 15:51     ` [Intel-wired-lan] " Alexander Lobakin
2023-05-22 16:05     ` Larysa Zaremba
2023-05-22 16:05       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:25 ` [PATCH RESEND bpf-next 04/15] ice: Make ptype internal to descriptor info processing Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:25 ` [PATCH RESEND bpf-next 05/15] ice: Introduce ice_xdp_buff Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-22 16:46   ` Alexander Lobakin
2023-05-22 16:46     ` [Intel-wired-lan] " Alexander Lobakin
2023-05-23  8:02     ` Larysa Zaremba
2023-05-23  8:02       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-25 11:02       ` Alexander Lobakin
2023-05-25 11:02         ` [Intel-wired-lan] " Alexander Lobakin
2023-05-12 15:25 ` [PATCH RESEND bpf-next 06/15] ice: Support HW timestamp hint Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:19   ` Stanislav Fomichev
2023-05-12 18:19     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-16 16:17     ` Jesper Dangaard Brouer
2023-05-16 16:17       ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-12 15:25 ` [PATCH RESEND bpf-next 07/15] ice: Support RX hash XDP hint Larysa Zaremba
2023-05-12 15:25   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:22   ` Stanislav Fomichev
2023-05-12 18:22     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-15 13:46     ` Larysa Zaremba
2023-05-15 13:46       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 08/15] ice: Support XDP hints in AF_XDP ZC mode Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 09/15] xdp: Add VLAN tag hint Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:28   ` Stanislav Fomichev
2023-05-12 18:28     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-15 15:36   ` Jesper Dangaard Brouer
2023-05-15 15:36     ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-15 16:09     ` Larysa Zaremba
2023-05-15 16:09       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-22  8:37       ` Jesper Dangaard Brouer
2023-05-22  8:37         ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-22 15:48         ` Larysa Zaremba
2023-05-22 15:48           ` [Intel-wired-lan] " Larysa Zaremba
2023-05-23 10:16           ` Jesper Dangaard Brouer
2023-05-23 10:16             ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-23 17:35             ` Larysa Zaremba
2023-05-23 17:35               ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 10/15] ice: Implement " Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:31   ` Stanislav Fomichev
2023-05-12 18:31     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-15 13:41     ` Larysa Zaremba
2023-05-15 13:41       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-15 15:07       ` Jesper Dangaard Brouer
2023-05-15 15:07         ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-15 15:45         ` Larysa Zaremba
2023-05-15 15:45           ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 11/15] xdp: Add checksum level hint Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:34   ` Stanislav Fomichev
2023-05-12 18:34     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-15 13:49     ` Larysa Zaremba
2023-05-15 13:49       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 12/15] ice: Implement " Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 13/15] selftests/bpf: Allow VLAN packets in xdp_hw_metadata Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:33   ` Stanislav Fomichev
2023-05-12 18:33     ` [Intel-wired-lan] " Stanislav Fomichev
2023-05-15 14:05     ` Larysa Zaremba
2023-05-15 14:05       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 15:26 ` [PATCH RESEND bpf-next 14/15] net, xdp: allow metadata > 32 Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-15 16:17   ` Jesper Dangaard Brouer
2023-05-15 16:17     ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-15 17:08     ` Larysa Zaremba
2023-05-15 17:08       ` [Intel-wired-lan] " Larysa Zaremba
2023-05-16 12:37       ` Alexander Lobakin
2023-05-16 12:37         ` [Intel-wired-lan] " Alexander Lobakin
2023-05-16 15:35         ` Jesper Dangaard Brouer
2023-05-16 15:35           ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-19 16:35           ` Alexander Lobakin
2023-05-19 16:35             ` [Intel-wired-lan] " Alexander Lobakin
2023-05-22 11:41             ` Jesper Dangaard Brouer
2023-05-22 11:41               ` [Intel-wired-lan] " Jesper Dangaard Brouer
2023-05-22 15:28               ` Alexander Lobakin
2023-05-22 15:28                 ` [Intel-wired-lan] " Alexander Lobakin
2023-05-22 15:55                 ` Daniel Borkmann
2023-05-22 15:55                   ` [Intel-wired-lan] " Daniel Borkmann
2023-05-12 15:26 ` [PATCH RESEND bpf-next 15/15] selftests/bpf: Add flags and new hints to xdp_hw_metadata Larysa Zaremba
2023-05-12 15:26   ` [Intel-wired-lan] " Larysa Zaremba
2023-05-12 18:37   ` Stanislav Fomichev
2023-05-12 18:37     ` [Intel-wired-lan] " Stanislav Fomichev

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=ZGuFNesdPS5ijl/R@lincoln \
    --to=larysa.zaremba@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrii@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.karlsson@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=mtahhan@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=xdp-hints@xdp-project.net \
    --cc=yhs@fb.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.