From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 3/3] ethdev: improve flow mark Rx offload deprecation notice
Date: Thu, 21 Nov 2019 23:01:23 +0100 [thread overview]
Message-ID: <3628380.zSPWDRPf13@xps> (raw)
In-Reply-To: <1574165536-2586-3-git-send-email-arybchenko@solarflare.com>
19/11/2019 13:12, Andrew Rybchenko:
> The deprecation notice is required since it adds more requirements
> when RTE flow mark and flag actions may be used and require
> changes in applications.
I am still not sure what is the best solution here.
I continued to think about it in this thread:
http://mails.dpdk.org/archives/dev/2019-November/151960.html
I think we cannot require any application change until 20.11
in order to keep API (and behaviour) compatibility.
If something would be implemented in 20.02,
it must be a new and optional API.
That's why I think no deprecation notice is required.
[...]
> +* ethdev: New offload flag ``DEV_RX_OFFLOAD_FLOW_MARK`` will be added in 20.02.
> + This will provide application an information if ``RTE_FLOW_ACTION_TYPE_MARK``
> + or ``RTE_FLOW_ACTION_TYPE_FLAG`` is supported and, what is more important,
> + allow an application to let PMD know that it would like to use these
> + features.
> + PMD may use the information to choose optimal datapath implementation and
> + configure HW appropriately to optimize performance and/or resources usage.
next prev parent reply other threads:[~2019-11-21 22:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:05 [dpdk-dev] [PATCH 1/3] ethdev: remove deprecation notice for packet type set Andrew Rybchenko
2019-11-19 12:05 ` [dpdk-dev] [PATCH 2/3] ethdev: remove deprecation notice about RSS hash offload Andrew Rybchenko
2019-11-19 12:05 ` [dpdk-dev] [PATCH 3/3] ethdev: improve flow mark Rx offload deprecation notice Andrew Rybchenko
2019-11-19 12:12 ` [dpdk-dev] [PATCH v2 1/3] ethdev: remove deprecation notice for packet type set Andrew Rybchenko
2019-11-19 12:12 ` [dpdk-dev] [PATCH v2 2/3] ethdev: remove deprecation notice about RSS hash offload Andrew Rybchenko
2019-11-19 15:04 ` Ferruh Yigit
2019-11-25 16:38 ` Ferruh Yigit
2019-11-19 12:12 ` [dpdk-dev] [PATCH v2 3/3] ethdev: improve flow mark Rx offload deprecation notice Andrew Rybchenko
2019-11-21 22:01 ` Thomas Monjalon [this message]
2019-11-22 10:12 ` Andrew Rybchenko
2019-11-22 11:15 ` Thomas Monjalon
2019-11-22 11:53 ` Andrew Rybchenko
2019-11-22 13:32 ` Jerin Jacob
2019-11-22 18:58 ` Thomas Monjalon
2019-11-23 9:42 ` Jerin Jacob
2019-11-23 18:12 ` Thomas Monjalon
2019-11-25 10:44 ` Jerin Jacob
2019-11-25 11:39 ` Thomas Monjalon
2019-12-02 4:21 ` Jerin Jacob
2019-12-02 9:15 ` Thomas Monjalon
2019-12-02 11:09 ` Jerin Jacob
2019-12-02 11:57 ` Andrew Rybchenko
2019-12-05 8:12 ` Jerin Jacob
2019-12-09 9:17 ` Andrew Rybchenko
2019-12-16 7:38 ` Jerin Jacob
2019-12-16 10:02 ` Andrew Rybchenko
2019-11-19 15:04 ` [dpdk-dev] [PATCH v2 1/3] ethdev: remove deprecation notice for packet type set Ferruh Yigit
2019-11-25 16:38 ` Ferruh Yigit
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=3628380.zSPWDRPf13@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=pbhagavatula@marvell.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).