DPDK patches and discussions
 help / color / mirror / Atom feed
From: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
To: xhavli56@stud.fit.vutbr.cz
Cc: dev@dpdk.org, Jan Viktorin <viktorin@cesnet.cz>,
	Ori Kam <orika@nvidia.com>, Matan Azrad <matan@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	"Min Hu (Connor)" <humin29@huawei.com>
Subject: [dpdk-dev] [PATCH 0/4] doc: update RTE flow rule and bonding related info
Date: Wed, 21 Jul 2021 17:55:07 +0200	[thread overview]
Message-ID: <20210721155511.188604-1-xhavli56@stud.fit.vutbr.cz> (raw)

Based on discussion in thread [1], I propose changes in RTE Flow docs to
reflect the current state and findings from the discussion.

[1] https://mails.dpdk.org/archives/dev/2021-July/213360.html

Cc: Jan Viktorin <viktorin@cesnet.cz>
Cc: Ori Kam <orika@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>
Cc: Thomas Monjalon <thomas@monjalon.net>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: "Min Hu (Connor)" <humin29@huawei.com>

Martin Havlik (4):
  doc: clarify RTE flow behaviour on port stop/start
  doc: specify RTE flow create behaviour
  doc: update bonding mode 8023ad info
  doc: note that testpmd on mlx5 has dedicated queues problem

 doc/guides/nics/mlx5.rst                                 | 3 ++-
 doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst | 8 ++++++++
 doc/guides/prog_guide/rte_flow.rst                       | 4 ++++
 doc/guides/testpmd_app_ug/testpmd_funcs.rst              | 3 +++
 4 files changed, 17 insertions(+), 1 deletion(-)

-- 
1.8.3.1


                 reply	other threads:[~2021-07-21 15:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210721155511.188604-1-xhavli56@stud.fit.vutbr.cz \
    --to=xhavli56@stud.fit.vutbr.cz \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viktorin@cesnet.cz \
    /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).