From: Markus Elfring <Markus.Elfring@web.de>
To: Levi Yun <ppbuk5246@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] time/tick-sched: idle load balancing when nohz_full cpu becomes idle.
Date: Wed, 8 May 2024 20:38:56 +0200 [thread overview]
Message-ID: <b4156f2a-ea8d-483a-b485-db4b5a80b1fe@web.de> (raw)
In-Reply-To: <20240508172621.30069-1-ppbuk5246@gmail.com>
> When nohz_full CPU stops tick in tick_nohz_irq_exit(),
> It wouldn't be chosen to perform idle load balancing bacause it doesn't
…
> So, nohz_balance_enter_idle() could be called safely without !was_stooped
> check.
* Why did you repeat typos in this patch iteration?
* Would you like to take the relevance of imperative wordings for changelogs
better into account?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc7#n94
> ---
> kernel/time/tick-sched.c | 6 ++++--
Will further patch version descriptions become helpful behind the marker line?
Regards,
Markus
next prev parent reply other threads:[~2024-05-08 18:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 21:31 [PATCH] time/tick-sched: enable " Levi Yun
2024-05-08 9:18 ` Markus Elfring
2024-05-09 9:59 ` Dan Carpenter
2024-05-08 17:26 ` [PATCH v2] time/tick-sched: " Levi Yun
2024-05-08 18:38 ` Markus Elfring [this message]
2024-05-08 19:15 ` Yun Levi
2024-05-08 19:22 ` [PATCH v3] " Levi Yun
2024-05-09 6:28 ` Markus Elfring
2024-05-09 7:26 ` Yun Levi
2024-05-09 8:16 ` Markus Elfring
2024-05-09 9:22 ` Yun Levi
2024-05-09 9:40 ` [v3] " Markus Elfring
2024-05-09 9:29 ` [PATCH v4] " Levi Yun
2024-05-09 9:55 ` [v4] " Markus Elfring
2024-05-15 16:41 ` [PATCH v4] " Yun Levi
2024-05-15 22:52 ` Frederic Weisbecker
2024-05-16 5:29 ` Yun Levi
2024-05-16 7:56 ` Peter Zijlstra
2024-05-16 8:20 ` Yun Levi
2024-05-16 8:49 ` Peter Zijlstra
2024-05-16 11:25 ` Frederic Weisbecker
2024-05-16 12:43 ` Yun Levi
2024-05-16 14:00 ` Peter Zijlstra
2024-05-16 14:23 ` Frederic Weisbecker
2024-05-16 14:45 ` Peter Zijlstra
2024-05-16 15:02 ` Frederic Weisbecker
2024-05-16 15:19 ` Peter Zijlstra
2024-05-16 15:32 ` Frederic Weisbecker
2024-05-16 16:12 ` Yun Levi
2024-05-16 17:53 ` Peter Zijlstra
2024-05-17 14:50 ` Frederic Weisbecker
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=b4156f2a-ea8d-483a-b485-db4b5a80b1fe@web.de \
--to=markus.elfring@web.de \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ppbuk5246@gmail.com \
--cc=tglx@linutronix.de \
/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®