From: Andrew Rybchenko <firstname.lastname@example.org> To: Thomas Monjalon <email@example.com> Cc: Ferruh Yigit <firstname.lastname@example.org>, Pavan Nikhilesh <email@example.com>, Neil Horman <firstname.lastname@example.org>, "John McNamara" <email@example.com>, Marko Kovacevic <firstname.lastname@example.org>, <email@example.com> Subject: Re: [dpdk-dev] [PATCH v2 3/3] ethdev: improve flow mark Rx offload deprecation notice Date: Fri, 22 Nov 2019 13:12:10 +0300 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <3628380.zSPWDRPf13@xps> On 11/22/19 1:01 AM, Thomas Monjalon wrote: > 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. Expected, but still very disappointing. The feature is implemented by Pavan (@ Marvell), supported by me, used by Qi (@ Intel), looks better than alternatives from application developer point of view  and finally postponed for 1 year without really strong motivation. I disagree that it is tightly related to moving mark/flag to dynamic field/flag and absolutely blocked by it. Yes, I know that the are concerns from the very beginning, but the problem is explained  and clear and no full-featured alternative solution is suggested. Solution suggested by Ori has many significant drawbacks as explained in  and highlighted in further discussion.  http://email@example.com/  http://firstname.lastname@example.org/ > If something would be implemented in 20.02, > it must be a new and optional API. Flow mark and flag may work without the offload with some drivers, but some drivers require the offload to make it work. Flow API error should contain message which says that the offload is disabled and must be enabled. > 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 index 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 2019-11-22 10:12 ` Andrew Rybchenko [this message] 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 publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
DPDK patches and discussions Archives are clonable: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ firstname.lastname@example.org public-inbox-index dev Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/ public-inbox