[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200626125806.0b1831a1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 26 Jun 2020 12:58:06 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc: davem@...emloft.net, Alice Michael <alice.michael@...el.com>,
netdev@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com,
Alan Brady <alan.brady@...el.com>,
Phani Burra <phani.r.burra@...el.com>,
Joshua Hay <joshua.a.hay@...el.com>,
Madhu Chittim <madhu.chittim@...el.com>,
Pavan Kumar Linga <pavan.kumar.linga@...el.com>,
Donald Skidmore <donald.c.skidmore@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Sridhar Samudrala <sridhar.samudrala@...el.com>
Subject: Re: [net-next v3 11/15] iecm: Add splitq TX/RX
On Thu, 25 Jun 2020 19:07:33 -0700 Jeff Kirsher wrote:
> @@ -1315,7 +1489,18 @@ iecm_tx_splitq_clean(struct iecm_queue *tx_q, u16 end, int napi_budget,
> */
> static inline void iecm_tx_hw_tstamp(struct sk_buff *skb, u8 *desc_ts)
Pretty sure you don't need the inline here. It's static function with
one caller.
> {
> - /* stub */
> + struct skb_shared_hwtstamps hwtstamps;
> + u64 tstamp;
> +
> + /* Only report timestamp to stack if requested */
> + if (!likely(skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP))
> + return;
> +
> + tstamp = (desc_ts[0] | (desc_ts[1] << 8) | (desc_ts[2] & 0x3F) << 16);
> + hwtstamps.hwtstamp =
> + ns_to_ktime(tstamp << IECM_TW_TIME_STAMP_GRAN_512_DIV_S);
> +
> + skb_tstamp_tx(skb, &hwtstamps);
> }
Why is there time stamp reading support if you have no ts_info
configuration on ethtool side at all and no PHC support?
Powered by blists - more mailing lists