From: Richard Cochran <richardcochran@gmail.com>
To: "Zulkifli, Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>
Cc: "leon@kernel.org" <leon@kernel.org>,
"intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>,
"gal@nvidia.com" <gal@nvidia.com>,
"saeed@kernel.org" <saeed@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"andy@greyhouse.net" <andy@greyhouse.net>
Subject: Re: [Intel-wired-lan] [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets
Date: Fri, 21 Oct 2022 05:48:44 -0700 [thread overview]
Message-ID: <Y1KVLAR2Qi6JeSBj@hoboy.vegasvil.org> (raw)
In-Reply-To: <SJ1PR11MB6180F00C9051443BCEA22AB2B82D9@SJ1PR11MB6180.namprd11.prod.outlook.com>
On Fri, Oct 21, 2022 at 12:25:13AM +0000, Zulkifli, Muhammad Husaini wrote:
> Sorry for misinterpreting SOFTWARE as HARDWARE in my previous reply.
> DMA Timestamping is definitely better than SOFTWARE timestamp because
> we sample the time at the controller MAC level.
Do you have numbers to back up this claim?
> Could you please provide additional details about this? What do you meant by
> offering 1 HW Timestamp with many SW timestamps?
- Let the PTP stack use hardware time stamps.
- Let all other applications use software time stamps.
Hm?
Thanks,
Richard
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-10-21 12:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 1:07 [Intel-wired-lan] [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [Intel-wired-lan] [PATCH v2 1/5] ethtool: Add new hwtstamp flag Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [Intel-wired-lan] [PATCH v2 2/5] net-timestamp: Increase the size of tsflags Muhammad Husaini Zulkifli
2022-10-18 5:57 ` Paul Menzel
2022-10-18 12:42 ` Zulkifli, Muhammad Husaini
2022-10-18 1:07 ` [Intel-wired-lan] [PATCH v2 3/5] net: sock: extend SO_TIMESTAMPING for DMA Fetch Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [Intel-wired-lan] [PATCH v2 4/5] igc: Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-10-20 22:39 ` Jacob Keller
2022-10-18 1:07 ` [Intel-wired-lan] [PATCH v2 5/5] ethtool: Add support for HWTSTAMP_FILTER_DMA_TIMESTAMP Muhammad Husaini Zulkifli
2022-10-18 11:45 ` [Intel-wired-lan] [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets Richard Cochran
2022-10-18 14:12 ` Zulkifli, Muhammad Husaini
2022-10-19 2:37 ` Richard Cochran
2022-10-21 0:25 ` Zulkifli, Muhammad Husaini
2022-10-21 12:48 ` Richard Cochran [this message]
2022-10-21 15:16 ` Jakub Kicinski
2022-10-18 14:23 ` Gal Pressman
2022-10-19 14:23 ` Zulkifli, Muhammad Husaini
2022-10-23 7:15 ` Gal Pressman
2022-10-18 19:02 ` Jakub Kicinski
2022-10-20 2:16 ` Zulkifli, Muhammad Husaini
2022-10-20 2:47 ` Jakub Kicinski
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=Y1KVLAR2Qi6JeSBj@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=intel-wired-lan@osuosl.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@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