From: "Theodore Ts'o" <tytso@mit.edu>
To: adilger.kernel@dilger.ca, Shaoying Xu <shaoyi@amazon.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
benh@amazon.com
Subject: Re: [PATCH 0/1] [RESEND] ext4: fix lazy initialization next schedule time computation in more granular unit
Date: Thu, 7 Oct 2021 10:21:34 -0400 [thread overview]
Message-ID: <163361646350.569327.18128912303237466845.b4-ty@mit.edu> (raw)
In-Reply-To: <20210902164412.9994-1-shaoyi@amazon.com>
On Thu, 2 Sep 2021 16:44:11 +0000, Shaoying Xu wrote:
> Description
> ===========
> Ext4 FS has inappropriate implementations on the next schedule time calculation
> that use jiffies to measure the time for one request to zero out inode table. This
> actually makes the wait time effectively dependent on CONFIG_HZ, which is
> undesirable. We have observed on server systems with 100HZ some fairly long delays
> in initialization as a result. Therefore, we propose to use more granular unit to
> calculate the next schedule time.
>
> [...]
Applied, thanks!
[1/1] ext4: fix lazy initialization next schedule time computation in more granular unit
commit: 3782027982881d2c1105ffe058aecb69cc780dfa
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2021-10-07 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 16:44 [PATCH 0/1] [RESEND] ext4: fix lazy initialization next schedule time computation in more granular unit Shaoying Xu
2021-09-02 16:44 ` [PATCH 1/1] " Shaoying Xu
2021-09-20 19:56 ` [PATCH 0/1] [RESEND] " Shaoying Xu
2021-10-07 14:21 ` Theodore Ts'o [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=163361646350.569327.18128912303237466845.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=benh@amazon.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaoyi@amazon.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;
as well as URLs for NNTP newsgroup(s).