From: Frederic Weisbecker <frederic@kernel.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Joel Fernandes <joelaf@google.com>,
rcu@vger.kernel.org,
"Cc: Frederic Weisbecker" <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: Observation on NOHZ_FULL
Date: Mon, 29 Jan 2024 23:43:08 +0100 [thread overview]
Message-ID: <Zbgp_JJvdczGccV3@pavilion.home> (raw)
In-Reply-To: <b6672b7b-fed4-449b-90e5-216f8294c1c3@joelfernandes.org>
Le Mon, Jan 29, 2024 at 05:20:23PM -0500, Joel Fernandes a écrit :
> > If i do not miss something
> > the NO_HZ_FULL will disable the timer if there is only one task on CPU
> > so that running task benefits from not being interrupted thus gets more
> > CPU time.
>
> Yes, that's right. I believe it is well known that HPC-type of workloads benefit
> from FULL, however it has led to want to try it out for constrained system as
> well where CPU cycles are a premium, especially if the improvement is like what
> the report suggests (give or take the concerns/questions Paul raised).
I'll be unable to suggest anything related to that Bogomips calculation but
I must add something about HPC.
I have long believed that HPC would benefit from nohz_full but I actually never
heard of any user of that. The current known users of nohz_full are workloads
that don't use the kernel once the application is launched and do their own
stack of, for example, networking, talking directly to the device from
userspace. Using DPDK for example. These usecases are for extremely low latency
expectations (a single interrupt can make you lose).
HPC looks to me different, making use of syscalls and kernel for I/O. Nohz_full
may remove timer IRQs but it adds performance loss on kernel entry, making it
probably unsuitable there. But I might be wrong.
Thanks.
>
> Thanks,
>
> - Joel
>
next prev parent reply other threads:[~2024-01-29 22:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 17:47 Observation on NOHZ_FULL Joel Fernandes
2024-01-29 20:41 ` Paul E. McKenney
2024-01-29 22:16 ` Joel Fernandes
2024-01-30 6:58 ` Andrea Righi
2024-01-30 10:17 ` Paul E. McKenney
2024-01-30 11:06 ` Uladzislau Rezki
2024-01-30 11:27 ` Andrea Righi
2024-01-30 11:41 ` Uladzislau Rezki
2024-01-30 13:39 ` Paul E. McKenney
2024-02-06 17:51 ` Andrea Righi
2024-02-06 18:44 ` Paul E. McKenney
2024-02-07 13:04 ` Uladzislau Rezki
2024-02-07 15:12 ` Andrea Righi
2024-02-07 15:49 ` Joel Fernandes
2024-02-15 7:51 ` Andrea Righi
2024-02-15 13:15 ` Uladzislau Rezki
2024-02-15 14:02 ` Joel Fernandes
2024-02-07 15:48 ` Joel Fernandes
2024-02-07 16:31 ` Andrea Righi
2024-02-07 16:52 ` Joel Fernandes
2024-02-07 17:05 ` Andrea Righi
2024-02-08 5:54 ` Joel Fernandes
2024-02-08 6:55 ` Andrea Righi
2024-02-08 12:53 ` Uladzislau Rezki
2024-02-08 14:51 ` Uladzislau Rezki
2024-02-12 0:22 ` Joel Fernandes
2024-02-12 9:05 ` Uladzislau Rezki
2024-02-12 9:44 ` Uladzislau Rezki
2024-01-29 20:48 ` Uladzislau Rezki
2024-01-29 22:20 ` Joel Fernandes
2024-01-29 22:43 ` Frederic Weisbecker [this message]
2024-01-29 22:53 ` Joel Fernandes
2024-01-29 23:11 ` Frederic Weisbecker
2024-01-29 23:36 ` Joel Fernandes
2024-01-30 0:40 ` Paul E. McKenney
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=Zbgp_JJvdczGccV3@pavilion.home \
--to=frederic@kernel.org \
--cc=fweisbec@gmail.com \
--cc=joel@joelfernandes.org \
--cc=joelaf@google.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.com \
/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