From: Vladimir Oltean <olteanv@gmail.com>
To: davem@davemloft.net, jakub.kicinski@netronome.com
Cc: richardcochran@gmail.com, f.fainelli@gmail.com,
vivien.didelot@gmail.com, andrew@lunn.ch, netdev@vger.kernel.org,
Vladimir Oltean <olteanv@gmail.com>
Subject: [PATCH net-next 0/3] Improvements to SJA1105 DSA RX timestamping
Date: Fri, 27 Dec 2019 04:37:47 +0200 [thread overview]
Message-ID: <20191227023750.12559-1-olteanv@gmail.com> (raw)
This series makes the sja1105 DSA driver use a dedicated kernel thread
for RX timestamping, a process which is time-sensitive and otherwise a
bit fragile. This allows users to customize their system (probabil an
embedded PTP switch) fully and allocate the CPU bandwidth for the driver
to expedite the RX timestamps as quickly as possible.
While doing this conversion, add a function to the PTP core for
cancelling this kernel thread (function which I found rather strange to
be missing).
Vladimir Oltean (3):
ptp: introduce ptp_cancel_worker_sync
net: dsa: sja1105: Use PTP core's dedicated kernel thread for RX
timestamping
net: dsa: sja1105: Empty the RX timestamping queue on PTP settings
change
drivers/net/dsa/sja1105/sja1105_ptp.c | 36 +++++++++++++--------------
drivers/net/dsa/sja1105/sja1105_ptp.h | 1 +
drivers/ptp/ptp_clock.c | 6 +++++
include/linux/dsa/sja1105.h | 2 --
include/linux/ptp_clock_kernel.h | 7 ++++++
5 files changed, 32 insertions(+), 20 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-27 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 2:37 Vladimir Oltean [this message]
2019-12-27 2:37 ` [PATCH net-next 1/3] ptp: introduce ptp_cancel_worker_sync Vladimir Oltean
2019-12-27 2:37 ` [PATCH net-next 2/3] net: dsa: sja1105: Use PTP core's dedicated kernel thread for RX timestamping Vladimir Oltean
2019-12-27 5:28 ` kbuild test robot
2019-12-27 12:43 ` Vladimir Oltean
2019-12-27 2:37 ` [PATCH net-next 3/3] net: dsa: sja1105: Empty the RX timestamping queue on PTP settings change Vladimir Oltean
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=20191227023750.12559-1-olteanv@gmail.com \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vivien.didelot@gmail.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).