From: Richard Cochran <richardcochran@gmail.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Josh Triplett <josh@joshtriplett.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] make POSIX timers optional
Date: Wed, 21 Sep 2016 10:38:52 +0200 [thread overview]
Message-ID: <20160921083851.GA27145@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1609201833010.9311@knanqh.ubzr>
On Tue, Sep 20, 2016 at 06:47:02PM -0400, Nicolas Pitre wrote:
> IMHO it is much nicer for the poor user configuring the kernel to have a
> single configuration prompt for PTP support, and then have whatever
> driver that can provide a PTP clock just do it (or omit it) based on
> that single prompt. Prompting for PTP support for each individual
> ethernet driver is silly.
Embedded people like to optimize their systems. One pattern I have
more than once is that a multihomed design designates a special PTP
interface, often with a different HW than the other ports. PTP
support adds extra code into the hot path, and for that reason people
want to turn it off on interfaces that don't need it.
So Thomas' idea is a better solution. It reduces the tinification in
this area to a careful kernel configuration. Yes, that is more work
to configure than having one "big red button" to push. The burden is
on the tinification user to get this right, and that is the right way,
IMHO. After all, this can be scripted, and such users have to
configure very carefully in any case.
Thanks,
Richard
next prev parent reply other threads:[~2016-09-21 8:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 19:56 [PATCH v2 0/2] make POSIX timers optional Nicolas Pitre
2016-09-20 19:56 ` [PATCH 1/2] ptp_clock: allow for it to be optional Nicolas Pitre
2016-09-20 19:56 ` [PATCH 2/2] posix-timers: make it configurable Nicolas Pitre
2016-09-20 20:25 ` [PATCH v2 0/2] make POSIX timers optional Richard Cochran
2016-09-20 20:45 ` Richard Cochran
2016-09-20 20:58 ` Nicolas Pitre
2016-09-20 21:09 ` Thomas Gleixner
2016-09-20 22:47 ` Nicolas Pitre
2016-09-21 8:38 ` Richard Cochran [this message]
2016-09-21 10:27 ` Jiri Benc
2016-09-21 9:09 ` Thomas Gleixner
2016-09-21 10:20 ` Jiri Benc
2016-09-20 20:52 ` Nicolas Pitre
2016-09-22 6:09 ` David Miller
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=20160921083851.GA27145@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).