From: "Xing, Beilei" <beilei.xing@intel.com>
To: Antoine POLLENUS <a.pollenus@deltacast.tv>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Issues with rte_flow_destroy
Date: Thu, 27 May 2021 08:27:03 +0000 [thread overview]
Message-ID: <MN2PR11MB3807FD7A3871627FED02CDC0F7239@MN2PR11MB3807.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9cb9a449bf9d48bab080d0e33170c6b6@deltacast.tv>
Hi,
What's the DPDK version you used? With the latest DPDK version, there's no such issue.
BR,
Beilei
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Antoine POLLENUS
> Sent: Tuesday, May 25, 2021 8:34 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Issues with rte_flow_destroy
>
> Hi,
>
> I'm experiencing some issues using the flow API and a intel XXV710 (i40e).
>
> I managed to reproduce it in the flow filtering sample.
>
> I'm creating one flow than deleting it and then creating another with basic
> change #define SRC_IP ((0<<24) + (0<<16) + (0<<8) + 0) /* src ip = 0.0.0.0 */
> #define SRC_IP_1 ((192<<24) + (168<<16) + (1<<8) + 3) /* dest ip = 192.168.1.1
> */ #define DEST_IP ((192<<24) + (168<<16) + (1<<8) + 1) /* dest ip = 192.168.1.1
> */ #define DEST_IP_1 ((192<<24) + (168<<16) + (1<<8) + 2) /* dest ip =
> 192.168.1.1 */
>
> flow = generate_ipv4_flow(port_id, selected_queue,
> SRC_IP, EMPTY_MASK,
> DEST_IP, FULL_MASK, &error);
> if (!flow) {
> printf("Flow can't be created %d message: %s\n",
> error.type,
> error.message ? error.message : "(no stated reason)");
> rte_exit(EXIT_FAILURE, "error in creating flow");
> }
> //Deleting the rule
> int returned;
> returned = rte_flow_destroy(port_id, flow, &error);
> if(returned < 0)
> {
> printf("destroy %d message: %s\n",
> error.type,
> error.message ? error.message : "(no stated reason)");
> }
> //Generating another rule
> flow1 = generate_ipv4_flow(port_id, selected_queue,
> SRC_IP_1, FULL_MASK,
> DEST_IP_1, FULL_MASK, &error);
> if (!flow1) {
> printf("Flow can't be created %d message: %s\n",
> error.type,
> error.message ? error.message : "(no stated reason)");
> rte_exit(EXIT_FAILURE, "error in creating flow");
> }
>
> When doing that I always get an error on the second flow I want to add.
>
> Flow can't be created 13 message: Conflict with the first rule's input set.
>
> The rule is indeed in conflict because it uses the same as the previous but with
> the source IP changing and also the destination IP.
>
> The strange thing is that a destroy has been made on the previous rule and
> should not be there anymore....
>
> Am I doing something wrong or is there a bug in the destroy function ?
>
> Thank you in advance for your answer,
>
> Regards,
>
> Antoine Pollenus
next prev parent reply other threads:[~2021-05-27 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 12:34 Antoine POLLENUS
2021-05-27 8:27 ` Xing, Beilei [this message]
2021-05-26 7:10 Antoine POLLENUS
2021-05-28 9:23 Antoine POLLENUS
2021-06-01 11:54 Antoine POLLENUS
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=MN2PR11MB3807FD7A3871627FED02CDC0F7239@MN2PR11MB3807.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=a.pollenus@deltacast.tv \
--cc=users@dpdk.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 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).