From: Uladzislau Rezki <urezki@gmail.com>
To: Marcus Seyfarth <m.seyfarth@gmail.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
paulmck@kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>,
Ziwei Dai <ziwei.dai@unisoc.com>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: Fwd: [6.5.1] Slow boot and opening files (RIP: kvfree_rcu_bulk)
Date: Tue, 5 Sep 2023 20:46:55 +0200 [thread overview]
Message-ID: <ZPd3n09wxHLMj2Bm@pc636> (raw)
In-Reply-To: <CA+FbhJNQfGW5RMJc-WaOmjqmYuTnqdvRPYO_40TP5=P4LFPDYQ@mail.gmail.com>
On Tue, Sep 05, 2023 at 08:17:27PM +0200, Marcus Seyfarth wrote:
> Systemd-analyze shows also improvements. But still the firmware part looks
> suspicious:
>
> ❯ systemd-analyze
> Startup finished in 2min 42.000s (firmware) + 4.201s (loader) + 6.895s (kernel)
> + 1.541s (userspace) = 2min 54.640s
> graphical.target reached after 1.539s in userspace.
>
>
> Am Di., 5. Sept. 2023 um 20:12 Uhr schrieb Marcus Seyfarth <
> m.seyfarth@gmail.com>:
>
> 3. Could you please remove that patch(revert it) and try one more time?
>
>
> Okay, I've just removed that patch and indeed the warning is gone on my
> self-compiled 6.5.1 Kernel. I've attached the journalctl output. The slow
> boot remains though. But at least the performance in WebGL Aquarium is back
> where I expected it to be.
>
Good. Please do not include that patch on top of 6.5.1 and higher kernels. It just
breaks the things and is not considered as applicable, because the functionality
which improves reclaim process is in place.
As for slow boot up time, it is another issue and not related to RCU, IMHO.
--
Uladzislau Rezki
next prev parent reply other threads:[~2023-09-05 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 1:34 Fwd: [6.5.1] Slow boot and opening files (RIP: kvfree_rcu_bulk) Bagas Sanjaya
2023-09-03 3:29 ` Hugh Dickins
2023-09-03 10:45 ` Paul E. McKenney
[not found] ` <CA+FbhJOSfqcb3=ecL-y=13j81b1Ts13wHpzBSURyCRQUvd2NWQ@mail.gmail.com>
[not found] ` <c054b588-b029-4380-9ec5-4ae50ee37d08@paulmck-laptop>
[not found] ` <CA+FbhJO1FbOvP=GmUse-r8Yma1tSv6iqppDhz9Ut1JKpjN49qQ@mail.gmail.com>
[not found] ` <CA+FbhJPOkV4Xa7ZJ4QF2y_-5i24F+TkhByr=LzMPt9iy9EshSQ@mail.gmail.com>
[not found] ` <4009a6e0-198c-4f25-8e34-4774dcd8c537@paulmck-laptop>
[not found] ` <CA+FbhJPxU+QKf1tTBd8XcKcSsTeRmJ=ji_L4QYiad--hGqRB5w@mail.gmail.com>
2023-09-03 15:36 ` Paul E. McKenney
[not found] ` <CA+FbhJPtmFG2vKNXWr67Tuh-4HUi8n81PmKxwftv9iK1a3On-A@mail.gmail.com>
2023-09-04 11:23 ` Uladzislau Rezki
[not found] ` <CA+FbhJPNZ-E3e7WBH_jAvi3Rn-2gV4TVk9S9qmheXkqXw+Sakg@mail.gmail.com>
2023-09-04 15:05 ` Uladzislau Rezki
[not found] ` <CA+FbhJMr6LzmOpVNkYyiSERAsNEqqvQwQ7SwJK=CmwvV9d2Z-A@mail.gmail.com>
2023-09-04 16:53 ` Uladzislau Rezki
2023-09-04 19:13 ` Uladzislau Rezki
[not found] ` <CA+FbhJPNK=4s8J5OqOBaDC8EDNQzevQMQ+fwZnfxG92ReabQOA@mail.gmail.com>
[not found] ` <CA+FbhJMEqLycroz=J6VvC=4OBaJSwz8K+K6Zgki80M-5YdYp6A@mail.gmail.com>
2023-09-05 10:41 ` Uladzislau Rezki
2023-09-05 16:46 ` Uladzislau Rezki
[not found] ` <CA+FbhJOekDxBjQH6jUFXusgakRVx_Y0S3s5avko23c6XqCc2Mw@mail.gmail.com>
[not found] ` <CA+FbhJNQfGW5RMJc-WaOmjqmYuTnqdvRPYO_40TP5=P4LFPDYQ@mail.gmail.com>
2023-09-05 18:46 ` Uladzislau Rezki [this message]
[not found] ` <CA+FbhJO4xfdrUtZLWMRMaZdM2W-G+ZKtg9ESdwT8DUFJZKmW-Q@mail.gmail.com>
2023-09-06 10:31 ` Uladzislau Rezki
2023-09-11 13:25 ` Bagas Sanjaya
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=ZPd3n09wxHLMj2Bm@pc636 \
--to=urezki@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.seyfarth@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=ziwei.dai@unisoc.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