From: "Michael S. Tsirkin" <mst@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Andrew Melnychenko <andrew@daynix.com>
Subject: Re: [PATCH v3 01/11] tap: Remove tap_probe_vnet_hdr_len()
Date: Fri, 13 Oct 2023 09:55:22 -0400 [thread overview]
Message-ID: <20231013095407-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <74139826-7e06-48c0-bb1c-0b5bf708c808@daynix.com>
On Fri, Oct 13, 2023 at 01:14:32PM +0900, Akihiko Odaki wrote:
> On 2023/10/13 10:38, Jason Wang wrote:
> > On Wed, Oct 11, 2023 at 11:40 PM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
> > >
> > > It was necessary since an Linux older than 2.6.35 may implement the
> > > virtio-net header but may not allow to change its length. Remove it
> > > since such an old Linux is no longer supported.
> >
> > Where can I see this agreement?
>
> docs/about/build-platforms.rst says:
> > The project aims to support the most recent major version at all times
> > for up to five years after its initial release. Support for the
> > previous major version will be dropped 2 years after the new major
> > version is released or when the vendor itself drops support, whichever
> > comes first. In this context, third-party efforts to extend the
> > lifetime of a distro are not considered, even when they are endorsed
> > by the vendor (eg. Debian LTS); the same is true of repositories that
> > contain packages backported from later releases (e.g. Debian
> > backports). Within each major release, only the most recent minor
> > release is considered.
> >
> > For the purposes of identifying supported software versions available
> > on Linux, the project will look at CentOS, Debian, Fedora, openSUSE,
> > RHEL, SLES and Ubuntu LTS. Other distros will be assumed to ship
> > similar software versions.
>
> All of the previous major versions of these distributions ship far newer
> kernels.
>
> CentOS Stream 8 and RHEL 8 ship 4.18.0.
Yes but RHEL7 is still in full support.
> Debian bullseye ships 5.10.0.
> Fedora 37 ships 6.5.6.
> openSUSE Leap 15.4 ships 5.14.21.
> SLES 12 ships 4.12.14.
> Ubuntu 20.04 ships 5.4.
It does not matter that a newer version is shipped. What matters is
whether older one is still supported.
next prev parent reply other threads:[~2023-10-13 13:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:39 [PATCH v3 00/11] virtio-net RSS/hash report fixes Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 01/11] tap: Remove tap_probe_vnet_hdr_len() Akihiko Odaki
2023-10-13 1:38 ` Jason Wang
2023-10-13 4:14 ` Akihiko Odaki
2023-10-13 5:00 ` Jason Wang
2023-10-13 5:26 ` Akihiko Odaki
2023-10-13 14:17 ` Michael S. Tsirkin
2023-10-13 14:22 ` Akihiko Odaki
2023-10-13 14:32 ` Michael S. Tsirkin
2023-10-13 14:34 ` Akihiko Odaki
2023-10-13 15:01 ` Michael S. Tsirkin
2023-10-16 5:25 ` Jason Wang
2023-10-16 5:30 ` Akihiko Odaki
2023-10-13 13:55 ` Michael S. Tsirkin [this message]
2023-10-13 14:00 ` Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 02/11] tap: Remove qemu_using_vnet_hdr() Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 03/11] net: Move virtio-net header length assertion Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 04/11] net: Remove receive_raw() Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 05/11] tap: Shrink zeroed virtio-net header Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 06/11] virtio-net: Copy header only when necessary Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 07/11] virtio-net: Disable RSS on reset Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 08/11] virtio-net: Unify the logic to update NIC state for RSS Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 09/11] virtio-net: Return an error when vhost cannot enable RSS Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 10/11] virtio-net: Do not clear VIRTIO_NET_F_RSS Akihiko Odaki
2023-10-11 15:39 ` [PATCH v3 11/11] ebpf: Fix RSS error handling Akihiko Odaki
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=20231013095407-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=andrew@daynix.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yuri.benditovich@daynix.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 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.