From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: "NeilBrown" <neilb@suse.de>
Cc: "Jes Sorensen" <jes@trained-monkey.org>,
"Kernel.org-Linux-RAID" <linux-raid@vger.kernel.org>
Subject: Re: mdadm minimum kernel version requirements?
Date: Wed, 12 Apr 2023 15:52:36 +0200 [thread overview]
Message-ID: <20230412155236.00002f37@linux.intel.com> (raw)
In-Reply-To: <168116364433.24821.9557577764628245206@noble.neil.brown.name>
On Tue, 11 Apr 2023 07:54:04 +1000
"NeilBrown" <neilb@suse.de> wrote:
> On Tue, 11 Apr 2023, Jes Sorensen wrote:
> > Hi,
> >
> > I bumped the minimum kernel version required for mdadm to 2.6.32.
> >
> > Should we drop support for anything prior to 3.10 at this point, since
> > RHEL7 is 3.10 based and SLES12 seems to be 3.12 based.
> >
> > Thoughts?
>
> When you talk about changing the required kernel version, I would find
> it helpful if you at least mention what actual kernel features you now
> want to depend on - at least the more significant ones.
>
> Aside from features, I'd rather think about how old the kernel is.
> 2.6.32 is over 13 years old.
> 3.10 is very nearly 10 years old.
> If there is something significant that landed in 3.10 that we want to
> depend on, then requiring that seems perfectly reasonable.
>
> I think the oldest SLE kernel that you might care about would be 4.12
> (SLE12-SP5 - nearly 6 years old). Anyone using an older SLE release
> values stability over new functionality and is not going to be trialling
> a new mdadm.
>
> Thanks,
> NeilBrown
Agree with Neil. I have no strong recommendation. I'm not aware significant
feature that landed recently. I think that any kernel released around 5 ago
will be applicable.
Thanks,
Marusz
next prev parent reply other threads:[~2023-04-12 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 15:49 mdadm minimum kernel version requirements? Jes Sorensen
2023-04-10 21:54 ` NeilBrown
2023-04-12 13:52 ` Mariusz Tkaczyk [this message]
2023-05-08 20:22 ` Jes Sorensen
2023-05-08 21:04 ` NeilBrown
2023-05-09 17:27 ` Jes Sorensen
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=20230412155236.00002f37@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.