DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
	dev@dpdk.org, "Olivier Matz" <olivier.matz@6wind.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Elad Nachman" <eladv6@gmail.com>,
	"Igor Ryzhov" <iryzhov@nfware.com>, "Dan Gora" <dg@adax.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v5] doc: note KNI alternatives
Date: Thu, 24 Nov 2022 08:55:25 -0800	[thread overview]
Message-ID: <20221124085525.244a553b@hermes.local> (raw)
In-Reply-To: <20221124114041.3169291-1-ferruh.yigit@amd.com>

On Thu, 24 Nov 2022 11:40:40 +0000
Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> +* It is out-of-tree Linux kernel module and it can't be distributed as binary as
> +  part of operating system vendor DPDK packages. This makes it harder to
> +  consume, although it is always possible to compile it from the source code.

To be precise, there is no legal restriction here. Maybe something that describes
why the process is awkward.

* It is out-of-tree Linux kernel module which makes updating and distributing the
  driver more difficult. Most users end up building the KNI driver from source
  which requires the packages and tools to build kernel modules.

  reply	other threads:[~2022-11-24 16:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 17:31 [dpdk-dev] [PATCH] doc: note KNI alternatives and deprecation plan Ferruh Yigit
2021-06-23 18:33 ` Stephen Hemminger
2021-06-24  8:19   ` Ferruh Yigit
2021-07-30 12:48 ` Olivier Matz
2021-11-23 10:21   ` Ferruh Yigit
2021-08-20 12:58 ` David Marchand
2021-11-23 10:42   ` Ferruh Yigit
2021-11-23 12:08 ` [PATCH v2 1/2] doc: note KNI alternatives Ferruh Yigit
2021-11-23 12:08   ` [PATCH v2 2/2] doc: announce KNI deprecation Ferruh Yigit
2021-11-24 14:00     ` Thomas Monjalon
2021-11-24 13:58   ` [PATCH v2 1/2] doc: note KNI alternatives Thomas Monjalon
2021-11-24 14:19     ` Ferruh Yigit
2021-11-24 17:16 ` [PATCH v3 " Ferruh Yigit
2021-11-24 17:16   ` [PATCH v3 2/2] doc: announce KNI deprecation Ferruh Yigit
2022-07-11 14:47     ` Jerin Jacob
2022-07-13 10:01     ` Thomas Monjalon
2022-07-13 11:01       ` Bruce Richardson
2022-07-13 16:10     ` [PATCH v4] " Thomas Monjalon
2022-07-13 19:51       ` Thomas Monjalon
2022-07-15 15:33         ` Thomas Monjalon
2022-07-14  9:20       ` Bruce Richardson
2022-07-14 10:07         ` Thomas Monjalon
2022-07-14 14:50         ` Ferruh Yigit
2022-07-14 15:03           ` Ferruh Yigit
2022-07-15 15:32             ` Thomas Monjalon
2022-07-14  9:30       ` David Marchand
2021-12-01 16:31   ` [PATCH v3 1/2] doc: note KNI alternatives Morten Brørup
2022-11-24 10:31     ` Ferruh Yigit
2022-11-24 11:40   ` [PATCH v5] " Ferruh Yigit
2022-11-24 16:55     ` Stephen Hemminger [this message]
2022-11-24 17:08       ` Ferruh Yigit
2022-11-24 17:15     ` [PATCH v6] " Ferruh Yigit
2022-11-26 21:11       ` Thomas Monjalon

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=20221124085525.244a553b@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dg@adax.com \
    --cc=eladv6@gmail.com \
    --cc=ferruh.yigit@amd.com \
    --cc=iryzhov@nfware.com \
    --cc=mb@smartsharesystems.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).