From: Stephen Hemminger <stephen@networkplumber.org>
To: fengchengwen <fengchengwen@huawei.com>
Cc: Olivier Matz <olivier.matz@6wind.com>, <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@xilinx.com>,
"lihuisong@huawei.com" <lihuisong@huawei.com>
Subject: Re: Minutes of Technical Board Meeting, 2022-06-01
Date: Wed, 8 Jun 2022 18:31:27 -0700 [thread overview]
Message-ID: <20220608183127.45aa5228@hermes.local> (raw)
In-Reply-To: <3be02bac-9f7c-6e8d-e32c-95634ad2a248@huawei.com>
On Thu, 9 Jun 2022 08:41:35 +0800
fengchengwen <fengchengwen@huawei.com> wrote:
> [snip]
>
> >
> > 4) Removal of KNI
> > -----------------
> >
> > There is no more maintainer for KNI.
> >
> > A progressive removal proposal was made:
> > - add a message at runtime and/or compilation to announce deprecation
> > - remove KNI example after 22.11
> > - remove lib + kmod from main repo for 23.11
>
> We still use KNI in some business scenarios, and we want to maintain it in this case.
Why?
>
> I recommend Huisong Li (lihuisong@huawei.com) as the new maintainer of the KNI.
>
> He has been involved in the community for several years and submitted some
> bugfix patches of KNI.
KNI has several unfixable architectural issues.
It would never pass a full upstream kernel review.
I hope you realize the security impacts of this.
next prev parent reply other threads:[~2022-06-09 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:48 Olivier Matz
2022-06-09 0:41 ` fengchengwen
2022-06-09 1:31 ` Stephen Hemminger [this message]
2022-06-09 2:07 ` fengchengwen
2022-06-09 2:30 ` Stephen Hemminger
2022-06-30 12:05 ` David Marchand
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=20220608183127.45aa5228@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@xilinx.com \
--cc=lihuisong@huawei.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
/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).