From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Keith Wiles <keith.wiles@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
David Marchand <david.marchand@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Elad Nachman <eladv6@gmail.com>, Igor Ryzhov <iryzhov@nfware.com>,
Dan Gora <dg@adax.com>
Subject: Re: [PATCH v2 1/2] doc: note KNI alternatives
Date: Wed, 24 Nov 2021 14:58:03 +0100 [thread overview]
Message-ID: <2937060.Av0YGoZ78G@thomas> (raw)
In-Reply-To: <20211123120839.1740537-1-ferruh.yigit@intel.com>
23/11/2021 13:08, Ferruh Yigit:
> --- a/doc/guides/nics/tap.rst
> +++ b/doc/guides/nics/tap.rst
> @@ -1,6 +1,8 @@
> .. SPDX-License-Identifier: BSD-3-Clause
> Copyright(c) 2016 Intel Corporation.
>
> +.. _TunTap_PMD:
No need for such anchor at the beginning of a doc.
You can reference a document with :doc:
[...]
> +There are other alternatives to KNI, all are available in the upstream Linux:
> +
> +#. :ref:`virtio_user_as_exceptional_path`
> +
> +#. :ref:`TunTap_PMD` as wrapper to `Linux tun/tap
> + <https://www.kernel.org/doc/Documentation/networking/tuntap.txt>`_
What about pcap, AF_PACKET and AF_XDP PMDs?
next prev parent reply other threads:[~2021-11-24 13:58 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 ` Thomas Monjalon [this message]
2021-11-24 14:19 ` [PATCH v2 1/2] doc: note KNI alternatives 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
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=2937060.Av0YGoZ78G@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dg@adax.com \
--cc=eladv6@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=iryzhov@nfware.com \
--cc=keith.wiles@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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 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.