[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y09i12Wcqr0whToP@hoboy.vegasvil.org>
Date: Tue, 18 Oct 2022 19:37:11 -0700
From: Richard Cochran <richardcochran@...il.com>
To: "Zulkifli, Muhammad Husaini" <muhammad.husaini.zulkifli@...el.com>
Cc: "intel-wired-lan@...osl.org" <intel-wired-lan@...osl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"kuba@...nel.org" <kuba@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"Gunasekaran, Aravindhan" <aravindhan.gunasekaran@...el.com>,
"gal@...dia.com" <gal@...dia.com>,
"saeed@...nel.org" <saeed@...nel.org>,
"leon@...nel.org" <leon@...nel.org>,
"michael.chan@...adcom.com" <michael.chan@...adcom.com>,
"andy@...yhouse.net" <andy@...yhouse.net>,
"Gomes, Vinicius" <vinicius.gomes@...el.com>
Subject: Re: [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets
On Tue, Oct 18, 2022 at 02:12:37PM +0000, Zulkifli, Muhammad Husaini wrote:
> > What is the use case for reporting DMA transmit time?
So the use case (mentioned below) is TSN?
> > How is this better than using SOF_TIMESTAMPING_TX_SOFTWARE ?
>
> The ideal situation is to use SOF TIMESTAMPING TX SOFTWARE.
> Application side will undoubtedly want to utilize PHY timestamps as much as possible.
I'm asking about SOFTWARE not hardware time stamps.
> But if every application requested the HW Tx timestamp, especially during periods of high load like TSN,
> in some cases when the controller only supports 1 HW timestamp, it would be a disaster.
But can't you offer 1 HW time stamp with many SW time stamps?
Thanks,
Rihcard
Powered by blists - more mailing lists