From: Jacob Keller <jacob.e.keller@intel.com>
To: Vishvambar Panth S <vishvambarpanth.s@microchip.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<kuba@kernel.org>
Cc: <bryan.whitehead@microchip.com>, <UNGLinuxDriver@microchip.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<richardcochran@gmail.com>
Subject: Re: [PATCH v3 net-next] net: microchip: lan743x: improve throughput with rx timestamp config
Date: Fri, 20 Oct 2023 10:21:04 -0700 [thread overview]
Message-ID: <999161da-4f03-42db-b444-d9f094163479@intel.com> (raw)
In-Reply-To: <20231020185801.25649-1-vishvambarpanth.s@microchip.com>
On 10/20/2023 11:58 AM, Vishvambar Panth S wrote:
> Currently all RX frames are timestamped which results in a performance
> penalty when timestamping is not needed. The default is now being
> changed to not timestamp any Rx frames (HWTSTAMP_FILTER_NONE), but
> support has been added to allow changing the desired RX timestamping
> mode (HWTSTAMP_FILTER_ALL - which was the previous setting and
> HWTSTAMP_FILTER_PTP_V2_EVENT are now supported) using
> SIOCSHWTSTAMP. All settings were tested using the hwstamp_ctl application.
> It is also noted that ptp4l, when started, preconfigures the device to
> timestamp using HWTSTAMP_FILTER_PTP_V2_EVENT, so this driver continues
> to work properly "out of the box".
>
> Test setup: x64 PC with LAN7430 ---> x64 PC as partner
>
> iperf3 with - Timestamp all incoming packets:
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-5.05 sec 517 MBytes 859 Mbits/sec 0 sender
> [ 5] 0.00-5.00 sec 515 MBytes 864 Mbits/sec receiver
>
> iperf Done.
>
> iperf3 with - Timestamp only PTP packets:
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-5.04 sec 563 MBytes 937 Mbits/sec 0 sender
> [ 5] 0.00-5.00 sec 561 MBytes 941 Mbits/sec receiver
>
> Signed-off-by: Vishvambar Panth S <vishvambarpanth.s@microchip.com>
> ---
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2023-10-20 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 18:58 [PATCH v3 net-next] net: microchip: lan743x: improve throughput with rx timestamp config Vishvambar Panth S
2023-10-20 17:21 ` Jacob Keller [this message]
2023-10-24 8:20 ` patchwork-bot+netdevbpf
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=999161da-4f03-42db-b444-d9f094163479@intel.com \
--to=jacob.e.keller@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vishvambarpanth.s@microchip.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).