[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220122020854.GA23783@hoboy.vegasvil.org>
Date: Fri, 21 Jan 2022 18:08:54 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: Andrew Lunn <andrew@...n.ch>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Grygorii Strashko <grygorii.strashko@...com>,
Jakub Kicinski <kuba@...nel.org>,
Joakim Zhang <qiangqing.zhang@....com>,
Kurt Kanzenbach <kurt@...utronix.de>,
Miroslav Lichvar <mlichvar@...hat.com>,
Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH RFC V1 net-next 3/4] net: Let the active time stamping
layer be selectable.
On Fri, Jan 21, 2022 at 04:23:27PM +0000, Vladimir Oltean wrote:
> On Fri, Jan 21, 2022 at 07:28:20AM -0800, Richard Cochran wrote:
> > On Fri, Jan 21, 2022 at 02:50:36PM +0000, Vladimir Oltean wrote:
> > > So as I mentioned earlier, the use case would be hardware performance
> > > testing and diagnosing. You may consider that as not that important, but
> > > this is basically what I had to do for several months, and even wrote
> > > a program for that, that collects packet timestamps at all possible points.
> >
> > This is not possible without making a brand new CMSG to accommodate
> > time stamps from all the various layers.
> >
> > That is completely out of scope for this series.
> >
> > The only practical use case of this series is to switch from PHY back to MAC.
>
> I don't think my proposal is out of scope.
I don't see a way to implement your proposal at all.
If you want to implement your proposal and submit a patch series, I
will gladly drop mine in favor of yours. Otherwise, my series solves
a real world problem and improves the stack at least a little bit.
Thanks,
Richard
Powered by blists - more mailing lists