Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Bug Report High CPU Usage events_power_efficient
From:   Martin Zaharinov <micron10@gmail.com>
In-Reply-To: <20200708092848.GB405531@kroah.com>
Date:   Wed, 15 Jul 2020 08:50:13 +0300
Cc:     "linux-kernel@vger kernel. org" <linux-kernel@vger.kernel.org>,
        Florian Westphal <fw@strlen.de>,
        Eric Dumazet <edumazet@google.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B525BA20-4B39-4B31-9535-28A93C5B8332@gmail.com>
References: <E2C5FE67-C85E-469C-9B81-10F7555F836B@gmail.com>
 <91805D0F-2D74-4EA3-A2D7-13E4FBBEAB51@gmail.com>
 <6AD52867-83C1-4C6C-A0AE-4DE0D6C16310@gmail.com>
 <C89D167C-E03F-4116-9647-F50607DF3A45@gmail.com>
 <20200708070912.GA351187@kroah.com>
 <CALidq=UYNMxLQTT_D=EOESUxr82LYH04YCjT6igwqdnw3YwyiA@mail.gmail.com>
 <20200708092848.GB405531@kroah.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi=20

Oki i find the problem is come from nf_conntrack_core=20

I isolate problem in this part :

queue_delayed_work(system_power_efficient_wq, &conntrack_gc_work.dwork, =
HZ);


When package go to queue delayed in one moment if connection track is to =
big process to delayed go to lock and start high cpu load.

This is need to check and find solution=E2=80=A6

For now I remove queue_delayed_work and wait to check machine and will =
write status.

Martin

> On 8 Jul 2020, at 12:28, Greg KH <gregkh@linuxfoundation.org> wrote:
>=20
>=20
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> A: No.
> Q: Should I include quotations after my reply?
>=20
> http://daringfireball.net/2007/07/on_top
>=20
> On Wed, Jul 08, 2020 at 11:34:52AM +0300, Martin Zaharinov wrote:
>> Yes i search but not find any information.
>=20
> Please do the testing yourself, using 'git bisect' to find the =
offending
> commit.
>=20
> thanks,
>=20
> greg k-h