[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170722052914.yo62jqdqsdv4hc5q@localhost.localdomain>
Date: Sat, 22 Jul 2017 07:29:14 +0200
From: Richard Cochran <richardcochran@...il.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Sekhar Nori <nsekhar@...com>, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, Wingman Kwok <w-kwok2@...com>,
Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
Subject: Re: [PATCH 1/2] net: ethernet: ti: cpts: convert to use
kthread_worker
On Fri, Jul 21, 2017 at 06:49:42PM -0500, Grygorii Strashko wrote:
> There could be significant delay in CPTS work schedule under high system
> load and on -RT which could cause CPTS misbehavior due to internal counter
> overflow. Usage of own kthread_worker allows to avoid such kind of issues
> and makes it possible to tune priority of CPTS kthread_worker thread on -RT
> (thread name "cpts").
I have also seen excessive delays in the time stamp work from the
dp83640 under certain loads. Can we please implement this time stamp
kthread_worker in the PHC subsystem? That way, the facility can be
used by other drivers without code duplication.
Thanks,
Richard
Powered by blists - more mailing lists