From: Richard Cochran <richardcochran@gmail.com>
To: "Y.b. Lu" <yangbo.lu@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Madalin-cristian Bucur <madalin.bucur@nxp.com>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 09/10] dpaa_eth: add support for hardware timestamping
Date: Tue, 5 Jun 2018 06:57:49 -0700 [thread overview]
Message-ID: <20180605135748.mlarwiyzf2oe27ax@localhost> (raw)
In-Reply-To: <DB6PR0401MB2536376432EC481473A5B4A3F8660@DB6PR0401MB2536.eurprd04.prod.outlook.com>
On Tue, Jun 05, 2018 at 03:35:28AM +0000, Y.b. Lu wrote:
> [Y.b. Lu] Actually these timestamping codes affected DPAA networking performance in our previous performance test.
> That's why we used ifdef for it.
How much does time stamping hurt performance?
If the time stamping is compiled in but not enabled at run time, does
it still affect performace?
Thanks,
Richard
next prev parent reply other threads:[~2018-06-05 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 7:08 [PATCH 00/10] Support DPAA PTP clock and timestamping Yangbo Lu
2018-06-04 7:08 ` [PATCH 01/10] fsl/fman: share the event interrupt Yangbo Lu
2018-06-04 7:08 ` [PATCH 02/10] ptp: support DPAA FMan 1588 timer in ptp_qoriq Yangbo Lu
2018-06-04 7:08 ` [PATCH 03/10] dt-binding: ptp_qoriq: add DPAA FMan support Yangbo Lu
2018-06-04 7:08 ` [PATCH 04/10] powerpc/mpc85xx: move ptp timer out of fman in dts Yangbo Lu
2018-06-04 7:08 ` [PATCH 05/10] arm64: dts: fsl: move ptp timer out of fman Yangbo Lu
2018-06-04 7:08 ` [PATCH 06/10] fsl/fman: add set_tstamp interface Yangbo Lu
2018-06-04 7:08 ` [PATCH 07/10] fsl/fman_port: support getting timestamp field Yangbo Lu
2018-06-04 7:08 ` [PATCH 08/10] fsl/fman: define frame description command UPD Yangbo Lu
2018-06-04 7:08 ` [PATCH 09/10] dpaa_eth: add support for hardware timestamping Yangbo Lu
2018-06-04 13:49 ` Richard Cochran
2018-06-05 3:35 ` Y.b. Lu
2018-06-05 13:57 ` Richard Cochran [this message]
2018-06-06 11:48 ` Y.b. Lu
2018-06-04 7:08 ` [PATCH 10/10] dpaa_eth: add the get_ts_info interface for ethtool Yangbo Lu
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=20180605135748.mlarwiyzf2oe27ax@localhost \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yangbo.lu@nxp.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).