From: Jakub Kicinski <kuba@kernel.org>
To: Richard Cochran <richardcochran@gmail.com>
Cc: "Zulkifli,
Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>,
"intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"Gunasekaran, Aravindhan" <aravindhan.gunasekaran@intel.com>,
"gal@nvidia.com" <gal@nvidia.com>,
"saeed@kernel.org" <saeed@kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
"andy@greyhouse.net" <andy@greyhouse.net>,
"Gomes, Vinicius" <vinicius.gomes@intel.com>
Subject: Re: [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets
Date: Fri, 21 Oct 2022 08:16:37 -0700 [thread overview]
Message-ID: <20221021081637.5195953b@kernel.org> (raw)
In-Reply-To: <Y1KVLAR2Qi6JeSBj@hoboy.vegasvil.org>
On Fri, 21 Oct 2022 05:48:44 -0700 Richard Cochran wrote:
> > 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.
We do need HW stamps for congestion control, the Rx ring queuing
(as well as Tx ring scheduling jitter) is very often in 10s of msec.
Comparing the SW stamp to the HW stamp is where we derive the signal
that the system is under excessive load.
next prev parent reply other threads:[~2022-10-21 15:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 1:07 [PATCH v2 0/5] Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [PATCH v2 1/5] ethtool: Add new hwtstamp flag Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [PATCH v2 2/5] net-timestamp: Increase the size of tsflags Muhammad Husaini Zulkifli
2022-10-18 5:57 ` [Intel-wired-lan] " Paul Menzel
2022-10-18 12:42 ` Zulkifli, Muhammad Husaini
2022-10-18 1:07 ` [PATCH v2 3/5] net: sock: extend SO_TIMESTAMPING for DMA Fetch Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [PATCH v2 4/5] igc: Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-10-18 1:07 ` [PATCH v2 5/5] ethtool: Add support for HWTSTAMP_FILTER_DMA_TIMESTAMP Muhammad Husaini Zulkifli
2022-10-18 11:45 ` [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
2022-10-21 15:16 ` Jakub Kicinski [this message]
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=20221021081637.5195953b@kernel.org \
--to=kuba@kernel.org \
--cc=andy@greyhouse.net \
--cc=aravindhan.gunasekaran@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=intel-wired-lan@osuosl.org \
--cc=leon@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=saeed@kernel.org \
--cc=vinicius.gomes@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;
as well as URLs for NNTP newsgroup(s).