From: Richard Cochran <richardcochran@gmail.com>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: Richard Cochran <rcochran@linutronix.de>,
netdev@vger.kernel.org, Andre Guedes <andre.guedes@intel.com>,
Henrik Austad <henrik@austad.us>,
linux-kernel@vger.kernel.org,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>,
intel-wired-lan@lists.osuosl.org,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH RFC V1 net-next 0/6] Time based packet transmission
Date: Tue, 19 Sep 2017 18:46:15 +0200 [thread overview]
Message-ID: <20170919164615.mfv77pxuuyqc4zq4@localhost> (raw)
In-Reply-To: <20170919144302.GB4347@localhost>
On Tue, Sep 19, 2017 at 04:43:02PM +0200, Miroslav Lichvar wrote:
> If I understand it correctly, this also allows us to make a PTP/NTP
> "one-step" clock with HW that doesn't support it directly.
Cool, yeah, I hadn't thought of that, but it would work...
Thanks,
Richard
next prev parent reply other threads:[~2017-09-19 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 7:41 [PATCH RFC V1 net-next 0/6] Time based packet transmission Richard Cochran
2017-09-18 7:41 ` [PATCH RFC V1 net-next 1/6] net: Add a new socket option for a future transmit time Richard Cochran
2017-09-18 14:50 ` Richard Cochran
2017-09-18 15:18 ` Eric Dumazet
2017-09-18 7:41 ` [PATCH RFC V1 net-next 2/6] net: skbuff: Add a field to support time based transmission Richard Cochran
2017-09-18 15:14 ` Eric Dumazet
2017-09-18 7:41 ` [PATCH RFC V1 net-next 3/6] net: ipv4: raw: Hook into " Richard Cochran
2017-09-18 7:41 ` [PATCH RFC V1 net-next 4/6] net: ipv4: udp: " Richard Cochran
2017-09-18 7:41 ` [PATCH RFC V1 net-next 5/6] net: packet: " Richard Cochran
2017-09-18 7:41 ` [PATCH RFC V1 net-next 6/6] net: igb: Implement " Richard Cochran
2017-09-18 16:34 ` [PATCH RFC V1 net-next 0/6] Time based packet transmission David Miller
2017-12-05 21:22 ` Vinicius Costa Gomes
2017-09-19 14:43 ` Miroslav Lichvar
2017-09-19 16:46 ` Richard Cochran [this message]
2017-09-20 17:35 ` levipearson
2017-09-20 20:11 ` Richard Cochran
2017-10-18 22:18 ` Jesus Sanchez-Palencia
2017-10-19 20:44 ` 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=20170919164615.mfv77pxuuyqc4zq4@localhost \
--to=richardcochran@gmail.com \
--cc=andre.guedes@intel.com \
--cc=anna-maria@linutronix.de \
--cc=davem@davemloft.net \
--cc=henrik@austad.us \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesus.sanchez-palencia@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rcochran@linutronix.de \
--cc=tglx@linutronix.de \
/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