From: patchwork-bot+netdevbpf@kernel.org
To: Vishvambar Panth S <vishvambarpanth.s@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, kuba@kernel.org,
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: Tue, 24 Oct 2023 08:20:22 +0000 [thread overview]
Message-ID: <169813562269.30900.16324458745146490166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231020185801.25649-1-vishvambarpanth.s@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 21 Oct 2023 00:28:01 +0530 you 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".
>
> [...]
Here is the summary with links:
- [v3,net-next] net: microchip: lan743x: improve throughput with rx timestamp config
https://git.kernel.org/netdev/net-next/c/169e0a5e4320
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-24 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 18:58 Vishvambar Panth S
2023-10-20 17:21 ` Jacob Keller
2023-10-24 8:20 ` patchwork-bot+netdevbpf [this message]
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=169813562269.30900.16324458745146490166.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.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
Powered by JetHome