From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Thomas Monjalon <thomas@monjalon.net>,
Alexander Kotliarov <alexander.kotliarov@gmail.com>
Cc: users@dpdk.org, david.marchand@redhat.com,
ferruh.yigit@intel.com, bruce.richardson@intel.com,
stephen@networkplumber.org
Subject: Re: [dpdk-users] Changes to DPDK kmod drivers / backward compatibility within LTS rel.
Date: Fri, 30 Oct 2020 22:38:36 +0000 [thread overview]
Message-ID: <09f8238a-f92b-985e-c77c-0dfc0d6550f1@ashroe.eu> (raw)
In-Reply-To: <3222028.xZJDvd7WxQ@thomas>
On 29/10/2020 21:07, Thomas Monjalon wrote:
> 24/09/2020 19:12, Alexander Kotliarov:
>> Hi there!
>> I would like to find out what is the policy regarding changes to the DPDK's
>> kmod drivers such as igb_uio.ko within a DPDK's LTS release. Are these
>> changes backward compatible?
>> For example, is there a guarantee that an application built
>> against 19.11.5, where igb_uio.ko received changes,would run with this
>> driver built from 19.11.1 version?
>>
>> Does http://doc.dpdk.org/guides/contributing/stable.html section 8.4 apply
>> to kmod drivers as well?
>
> There is no such formal guarantee, but in my opinion,
> it should be the case. Do you imagine a change in kmod
> which could break a DPDK version?
>
We never said anything specifically about the kmods (kni or igb_uio).
There is always a possibility a change here could break DPDK, however remote.
More probable for KNI than igb_uio.
Ray K
prev parent reply other threads:[~2020-10-30 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 17:12 Alexander Kotliarov
2020-10-29 21:07 ` Thomas Monjalon
2020-10-29 21:49 ` Stephen Hemminger
2020-10-30 22:38 ` Kinsella, Ray [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=09f8238a-f92b-985e-c77c-0dfc0d6550f1@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=alexander.kotliarov@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/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).