mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Zaharinov <micron10@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger kernel. org" <linux-kernel@vger.kernel.org>,
	Florian Westphal <fw@strlen.de>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: Bug Report High CPU Usage events_power_efficient
Date: Wed, 15 Jul 2020 08:50:13 +0300	[thread overview]
Message-ID: <B525BA20-4B39-4B31-9535-28A93C5B8332@gmail.com> (raw)
In-Reply-To: <20200708092848.GB405531@kroah.com>

Hi 

Oki i find the problem is come from nf_conntrack_core 

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…

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:
> 
> 
> 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?
> 
> http://daringfireball.net/2007/07/on_top
> 
> On Wed, Jul 08, 2020 at 11:34:52AM +0300, Martin Zaharinov wrote:
>> Yes i search but not find any information.
> 
> Please do the testing yourself, using 'git bisect' to find the offending
> commit.
> 
> thanks,
> 
> greg k-h


      reply	other threads:[~2020-07-15  5:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 12:55 Martin Zaharinov
2020-07-07 19:44 ` Martin Zaharinov
2020-07-07 19:54   ` Martin Zaharinov
2020-07-08  6:50     ` Martin Zaharinov
2020-07-08  7:09       ` Greg KH
2020-07-08  8:34         ` Martin Zaharinov
2020-07-08  9:28           ` Greg KH
2020-07-15  5:50             ` Martin Zaharinov [this message]

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=B525BA20-4B39-4B31-9535-28A93C5B8332@gmail.com \
    --to=micron10@gmail.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®