From: "Köry Maincent" <kory.maincent@bootlin.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Max Georgiev <glipus@gmail.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
kuba@kernel.org, netdev@vger.kernel.org,
maxime.chevallier@bootlin.com
Subject: Re: [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set
Date: Tue, 4 Apr 2023 09:57:10 +0200 [thread overview]
Message-ID: <20230404095710.73c47c20@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <d6f905fd-9bd3-b673-710a-cbd080342d0e@linux.dev>
On Mon, 3 Apr 2023 18:18:18 +0100
Vadim Fedorenko <vadim.fedorenko@linux.dev> wrote:
> On 03/04/2023 16:42, Max Georgiev wrote:
> > On Mon, Apr 3, 2023 at 6:26 AM Vladimir Oltean <vladimir.oltean@nxp.com>
> > wrote:
> >>
> >> On Sun, Apr 02, 2023 at 08:24:35AM -0600, Maxim Georgiev wrote:
> >>> Current NIC driver API demands drivers supporting hardware timestamping
> >>> to support SIOCGHWTSTAMP/SIOCSHWTSTAMP IOCTLs. Handling these IOCTLs
> >>> requires dirivers to implement request parameter structure translation
> >>> between user and kernel address spaces, handling possible
> >>> translation failures, etc. This translation code is pretty much
> >>> identical across most of the NIC drivers that support SIOCGHWTSTAMP/
> >>> SIOCSHWTSTAMP.
> >>> This patch extends NDO functiuon set with ndo_hwtstamp_get/set
> >>> functions, implements SIOCGHWTSTAMP/SIOCSHWTSTAMP IOCTL translation
> >>> to ndo_hwtstamp_get/set function calls including parameter structure
> >>> translation and translation error handling.
> >>>
> >>> This patch is sent out as RFC.
> >>> It still pending on basic testing.
> >>
> >> Who should do that testing? Do you have any NIC with the hardware
> >> timestamping capability?
> >
> > I'm planning to do the testing with netdevsim. I don't have access to
> > any NICs with
> > hardware timestamping support.
> >
>
> Hi Max!
> I might do some manual tests with the hardware that support timestamping
> once you respin the series with the changes discussed in the code
> comments. I'll convert hardware drivers myself to support new NDO on top
> of your patches.
Same here.
Köry,
next prev parent reply other threads:[~2023-04-04 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 14:24 [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set Maxim Georgiev
2023-04-02 18:23 ` Gerhard Engleder
2023-04-03 1:10 ` Max Georgiev
2023-04-03 12:26 ` Vladimir Oltean
2023-04-03 15:42 ` Max Georgiev
2023-04-03 17:18 ` Vadim Fedorenko
2023-04-04 7:57 ` Köry Maincent [this message]
2023-04-05 3:07 ` Max Georgiev
2023-04-04 12:30 ` Vladimir Oltean
2023-04-04 23:25 ` Jakub Kicinski
2023-04-05 6:42 ` Max Georgiev
2023-04-05 12:06 ` Vladimir Oltean
2023-04-03 21:19 ` Jakub Kicinski
2023-04-03 22:48 ` Richard Cochran
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=20230404095710.73c47c20@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=glipus@gmail.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--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