public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, yi.zhang@huawei.com,
	jack@suse.cz, tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	yukuai3@huawei.com, niecheng1@uniontech.com,
	zhangdandan@uniontech.com, guanwentao@uniontech.com
Subject: Re: [PATCH v2 4.19 0/4] ext4: improve delalloc buffer write performance
Date: Tue, 23 Jul 2024 19:58:16 +0200	[thread overview]
Message-ID: <2024072316-thirty-cytoplasm-2b81@gregkh> (raw)
In-Reply-To: <78C2D546AD199A57+20240720160420.578940-1-wangyuli@uniontech.com>

On Sun, Jul 21, 2024 at 12:04:06AM +0800, WangYuli wrote:
> Changes since v1:
>   Fixed some formatting errors to make the patchset less confusing.
> 
> A patchset from linux-5.15 should be backported to 4.19 that can
> significantly improve ext4 fs read and write performance. Unixbench test
> results for linux-4.19.318 on Phytium D2000 CPU are shown below.

Also, this looks like a performance issue, why not just use a newer
kernel (i.e. 5.15.y) to get the benefit of this, and many other,
increased performance fixes?  4.19.y is only going to be alive for a few
more months, if you haven't already planned to move off of it yet, you
need to do so now.

thanks,

greg k-h

  parent reply	other threads:[~2024-07-23 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20 16:04 [PATCH v2 4.19 0/4] ext4: improve delalloc buffer write performance WangYuli
2024-07-23 17:57 ` Greg KH
2024-07-23 17:58 ` Greg KH [this message]
2024-07-24  4:55   ` WangYuli
2024-07-24  5:23     ` Greg KH

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=2024072316-thirty-cytoplasm-2b81@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=guanwentao@uniontech.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niecheng1@uniontech.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=wangyuli@uniontech.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.com \
    --cc=zhangdandan@uniontech.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