From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: dev@dpdk.org, orika@nvidia.com, ferruh.yigit@intel.com,
andrew.rybchenko@oktetlabs.ru, ajit.khaparde@broadcom.com,
jerinj@marvell.com
Subject: Re: [dpdk-dev] [RFC PATCH 0/2] Flow entities behavior across port restart
Date: Tue, 05 Oct 2021 19:23:06 +0200 [thread overview]
Message-ID: <2075143.HYUFLV3GoE@thomas> (raw)
In-Reply-To: <20210901085516.3647814-1-dkozlyuk@nvidia.com>
> Dmitry Kozlyuk (2):
> ethdev: add capability to keep flow rules on restart
> ethdev: add capability to keep indirect actions on restart
>
> doc/guides/prog_guide/rte_flow.rst | 21 +++++++++++++++++++++
> lib/ethdev/rte_ethdev.h | 7 +++++++
> 2 files changed, 28 insertions(+)
We should update this:
* Please note that some configuration is not stored between calls to
* rte_eth_dev_stop()/rte_eth_dev_start(). The following configuration will
* be retained:
*
* - MTU
* - flow control settings
* - receive mode configuration (promiscuous mode, all-multicast mode,
* hardware checksum mode, RSS/VMDQ settings etc.)
* - VLAN filtering configuration
* - default MAC address
* - MAC addresses supplied to MAC address array
* - flow director filtering mode (but not filtering rules)
* - NIC queue statistics mappings
prev parent reply other threads:[~2021-10-05 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:55 Dmitry Kozlyuk
2021-09-01 8:55 ` [dpdk-dev] [RFC PATCH 1/2] ethdev: add capability to keep flow rules on restart Dmitry Kozlyuk
2021-09-01 8:55 ` [dpdk-dev] [RFC PATCH 2/2] ethdev: add capability to keep indirect actions " Dmitry Kozlyuk
2021-09-27 11:21 ` Dmitry Kozlyuk
2021-10-06 17:12 ` Ajit Khaparde
2021-10-07 8:16 ` Dmitry Kozlyuk
2021-10-11 13:58 ` Andrew Rybchenko
2021-10-11 15:53 ` Ori Kam
2021-10-12 9:15 ` Andrew Rybchenko
2021-10-12 10:26 ` Ori Kam
2021-10-12 10:41 ` Andrew Rybchenko
2021-10-13 8:36 ` Dmitry Kozlyuk
2021-10-11 15:57 ` Dmitry Kozlyuk
2021-10-05 17:23 ` Thomas Monjalon [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=2075143.HYUFLV3GoE@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.com \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=orika@nvidia.com \
/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).