[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADEbmW0knbPw7R5_Z+GYs2-QkEP4tU4iXw6RtsnXvAFxJZ4GRg@mail.gmail.com>
Date: Mon, 3 Apr 2023 15:36:52 +0200
From: Michal Schmidt <mschmidt@...hat.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>,
Michal Michalik <michal.michalik@...el.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
Karol Kolacinski <karol.kolacinski@...el.com>,
Petr Oros <poros@...hat.com>
Subject: Re: [PATCH net-next 1/4] ice: lower CPU usage of the GNSS read thread
On Sat, Apr 1, 2023 at 8:31 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> On Sat, Apr 01, 2023 at 07:26:56PM +0200, Michal Schmidt wrote:
> > The ice-gnss-<dev_name> kernel thread, which reads data from the u-blox
> > GNSS module, keep a CPU core almost 100% busy. The main reason is that
> > it busy-waits for data to become available.
>
> Hi Michal
>
> Please could you change the patch subject. Maybe something like "Do
> not busy wait in read" That gives a better idea what the patch does.
And I thought I was doing so well with the subjects :)
OK, I will change it.
Before resending, I would like to get a comment from Intel about that
special 0.1 s interval. If it turns out it is not necessary, I would
simplify the patch further.
Thanks!
Michal
Powered by blists - more mailing lists