netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Georgiev <glipus@gmail.com>
To: glipus@gmail.com, kory.maincent@bootlin.com
Cc: kuba@kernel.org, netdev@vger.kernel.org,
	maxime.chevallier@bootlin.com, vladimir.oltean@nxp.com,
	vadim.fedorenko@linux.dev, richardcochran@gmail.com,
	gerhard@engleder-embedded.com
Subject: [RFC PATCH v4 0/5] New NDO methods ndo_hwtstamp_get/set
Date: Sat, 22 Apr 2023 21:24:37 -0600	[thread overview]
Message-ID: <20230423032437.285014-1-glipus@gmail.com> (raw)

This stack of patches introduces a couple of new NDO methods,
ndo_hwtstamp_get and ndo_hwtstamp_set. These new methods can be
implemented by NIC drivers to allow setting and querying HW
timestamp settings. Drivers implementing these methods will
not need to handle SIOCGHWTSTAMP/SIOCSHWTSTAMP IOCTLs.
The new NDO methods will handle copying request parameters
between user address space and kernel space.

Maxim Georgiev (5):
  Add NDOs for hardware timestamp get/set
  Add ifreq pointer field to kernel_hwtstamp_config structure
  Add ndo_hwtstamp_get/set support to vlan/maxvlan code path
  Add ndo_hwtstamp_get/set support to bond driver
  Implement ndo_hwtstamp_get/set methods in netdevsim driver

 drivers/net/bonding/bond_main.c   | 106 +++++++++++++++++-----------
 drivers/net/macvlan.c             |  34 ++++-----
 drivers/net/netdevsim/ethtool.c   |  11 +++
 drivers/net/netdevsim/netdev.c    |  24 +++++++
 drivers/net/netdevsim/netdevsim.h |   1 +
 include/linux/net_tstamp.h        |  15 ++++
 include/linux/netdevice.h         |  22 ++++++
 net/8021q/vlan_dev.c              |  25 +++++--
 net/core/dev_ioctl.c              | 110 +++++++++++++++++++++++++++++-
 9 files changed, 279 insertions(+), 69 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-23  3:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  3:24 Maxim Georgiev [this message]
2023-04-26 16:58 ` [RFC PATCH v4 0/5] New NDO methods ndo_hwtstamp_get/set Köry Maincent
2023-04-27  4:00   ` Max Georgiev
2023-04-27  8:43     ` Köry Maincent
2023-04-28  4:57       ` Max Georgiev
2023-04-28  8:11         ` Köry Maincent
2023-04-28 14:14           ` Max Georgiev
2023-04-28 14:34             ` Köry Maincent
2023-04-29 19:44             ` Vadim Fedorenko
2023-05-02  4:35               ` Max Georgiev
2023-05-02  4:44                 ` Max Georgiev
2023-05-02  9:13                   ` Köry Maincent

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=20230423032437.285014-1-glipus@gmail.com \
    --to=glipus@gmail.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=vladimir.oltean@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).