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,
chenyichong@uniontech.com, wentao@uniontech.com
Subject: Re: [PATCH v2 4.19 0/4] ext4: improve delalloc buffer write performance
Date: Wed, 24 Jul 2024 07:23:20 +0200 [thread overview]
Message-ID: <2024072434-clunky-ninja-89fa@gregkh> (raw)
In-Reply-To: <206F8E88DD4C4DD9+5197bc65-d440-4ad5-8b19-e1f83f4a1c7a@uniontech.com>
On Wed, Jul 24, 2024 at 12:55:52PM +0800, WangYuli wrote:
> Hi greg k-h,
>
> As a commercial Linux distribution maintainer, we understand that
> even though upstream support for linux-4.19.y is ending, our users'
> reliance on this kernel version will not cease immediately.
Good luck to them, given that almost immediately after it goes out of
support it will become insecure :(
> They often lack the time or resources to promptly migrate all their
> devices to a newer kernel, due to considerations such as stability,
> operational costs, and other factors.
They have had 6 years to plan for this, how much time do they need?
> Therefore, to provide a more graceful conclusion to the linux-4.19.y
> lifecycle, we propose backporting these performance optimizations
> to extend its useful life and ensure a smooth transition for commercial
> users by the way.
Performance optimizations for old kernels like this are not a good idea,
please just have them move to a more modern, and actually supported,
kernel instead if they wish to have performance improvements. Otherwise
you are ensuring they will never move.
good luck!
greg k-h
prev parent reply other threads:[~2024-07-24 5:23 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
2024-07-24 4:55 ` WangYuli
2024-07-24 5:23 ` Greg KH [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=2024072434-clunky-ninja-89fa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=chenyichong@uniontech.com \
--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=wentao@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