DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anandaraman Viswanathan <anandaramanv@hcl.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "helin.zhang@intel.com" <helin.zhang@intel.com>,
	Rajaraman Balasubramanian <RajaramanB@hcl.com>,
	"Gunaseelan Venkatachary - ERS, HCL Tech" <gunaseelanv@hcl.com>,
	Santosh Sethupathi <sethupathis@hcl.com>,
	"Salvatore Morsa" <salvatore.morsa@hcl.com>
Subject: [dpdk-dev] RSS handling using L2_Payload type - Flexible Payload
Date: Wed, 13 Feb 2019 05:37:50 +0000	[thread overview]
Message-ID: <SG2PR04MB3771881FFFCF0F5F0FA2C993D0660@SG2PR04MB3771.apcprd04.prod.outlook.com> (raw)

Hi Team,
This is regarding RSS feature. In RSS configuration with Flexible Payload, facing a problem in getting packets distributed across multiple queues (2 per port). While debugging, found packets going thru q1 even if million packets are sent.
For simulating multiple flows, modifying Inner Payload which has one more Ethernet header, Src and Dest MAC of that header are getting changed incrementally for each packet.


To further validate if FVL support RSS L2_PAYLOAD , we used the function rte_eth_dev_info_get() to check RSS offloads in dev_info struct,  It outputs "hash_key_size:52 flow_type_rss_offloads:0x7ef8", which means RSS supports L2_PAYLOAD.


The details of configuration and code snippets given below

struct rte_eth_hash_filter_info filter_info;



    memset(&filter_info, 0, sizeof(filter_info));



    filter_info.info_type = RTE_ETH_HASH_FILTER_INPUT_SET_SELECT;

    filter_info.info.input_set_conf.flow_type = RTE_ETH_FLOW_L2_PAYLOAD;

    filter_info.info.input_set_conf.inset_size = 8;



    filter_info.info.input_set_conf.field[0] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_1ST_WORD;

    filter_info.info.input_set_conf.field[1] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_2ND_WORD;

    filter_info.info.input_set_conf.field[2] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_3RD_WORD;

    filter_info.info.input_set_conf.field[3] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_4TH_WORD;

    filter_info.info.input_set_conf.field[4] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_5TH_WORD;

    filter_info.info.input_set_conf.field[5] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_6TH_WORD;

    filter_info.info.input_set_conf.field[6] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_7TH_WORD;

    filter_info.info.input_set_conf.field[7] = RTE_ETH_INPUT_SET_FLEX_PAYLOAD_8TH_WORD;



    filter_info.info.input_set_conf.op = RTE_ETH_INPUT_SET_ADD;



    filter_ret = rte_eth_dev_filter_ctrl(xd->port_id, RTE_ETH_FILTER_HASH, RTE_ETH_FILTER_SET, &filter_info);



MACRO  "RTE_ETH_FLOW_L2_PAYLOAD " has been used to set RSS flow type, wish to check if this approach is good OR Any prerequisites in config to be done OR Any further changes needed in the code.



Hello Helin

Copying you as we see from DPDK forum (http://mails.dpdk.org/archives/dev/2015-November/027203.html<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmails.dpdk.org%2Farchives%2Fdev%2F2015-November%2F027203.html&data=02%7C01%7Canandaramanv%40hcl.com%7Cc025657b0204440f34c208d6916ece50%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636856302422857253&sdata=gKc0dDAnCkGR8F3wL6P5kUCRfIOBXGoskIU3j9RAQi4%3D&reserved=0> ), you are the author of above feature in DPDK , hence wish to request for clarifying our understanding on RSS as mentioned above is correct.


Cheers
Anand

::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 reply	other threads:[~2019-02-13  5:38 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=SG2PR04MB3771881FFFCF0F5F0FA2C993D0660@SG2PR04MB3771.apcprd04.prod.outlook.com \
    --to=anandaramanv@hcl.com \
    --cc=RajaramanB@hcl.com \
    --cc=dev@dpdk.org \
    --cc=gunaseelanv@hcl.com \
    --cc=helin.zhang@intel.com \
    --cc=salvatore.morsa@hcl.com \
    --cc=sethupathis@hcl.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).