DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Havlík Martin" <xhavli56@stud.fit.vutbr.cz>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jan Viktorin <viktorin@cesnet.cz>,
	dev@dpdk.org, chas3@att.com, humin29@huawei.com,
	thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru,
	haiyue.wang@intel.com, ivan.ilchenko@oktetlabs.ru,
	aman.deep.singh@intel.com, kirankn@juniper.net,
	lirongqing@baidu.com, ajit.khaparde@broadcom.com,
	Ori Kam <orika@nvidia.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] net/bonding: fix dedicated queues flow rule issue
Date: Sun, 07 Nov 2021 12:03:38 +0100	[thread overview]
Message-ID: <012de0bf4972b7c2f4534043038b451c@stud.fit.vutbr.cz> (raw)
In-Reply-To: <6c5a60db-4062-ad0f-5298-baa91553a1f1@intel.com>

Dne 2021-10-27 11:55, Ferruh Yigit napsal:
> On 10/5/2021 6:16 PM, Martin Havlik wrote:
>> This patchset stems from [1].
>> 
>> Not all PMDs allow RTE flow rule creation before device start.
>> Introduced capability marks the ones that allow it.
>> The capability is then used to fix flow rule creation for
>> dedicated queues in slave devices in bonding.
>> 
>> The introduced capa _will need to be set_ for all appropriate PMDs
>> in `rte_eth_dev_info->dev_capa`.
>> That is not pretty, but it holds the semantics of a capability
>> correctly, as opposed to making it a requirement to have the device
>> started before creating flow rules.
>> 
> 
> +Ori & Dmitry.
> 
> I think right now the method to check if device supports adding flow
> rules when stopped is run 'rte_flow_create()' when device is stopped
> and check return value.
> 
> Can we do similar in the bonding?
It might be a possible solution. The only thing I'm not sure about is 
that different PMDs may require different flow rule specifications for 
the rule to be valid, e.g. what pattern and action to set to this tryout 
flow rule? We would have to make sure the rule can be created on any PMD 
so failure would mean only one thing - device doesn't support creating 
flow rules when stopped.

Is that possible? Is it already a thing that is used somewhere?
> 
> I am not clear if there is an error to differentiate flow create is
> failed because device is stopped (or from some other reason).
> 
> 
> And other option is, what happens if rule is always created after
> device started?
That is what I originally proposed [here], but it didn't gain much 
favour so the idea got lost in the discussion.

[here] https://mails.dpdk.org/archives/dev/2021-June/212210.html
> 
>> [1] https://www.mail-archive.com/dev@dpdk.org/msg214840.html
>> 
>> Martin Havlik (2):
>>    lib/ethdev: introduce RTE_ETH_DEV_CAPA_FLOW_CREATE_BEFORE_START
>>    net/bonding: require started device for dedicated queues
>> 
>>   drivers/net/bonding/rte_eth_bond_pmd.c | 25 
>> +++++++++++++++++++------
>>   lib/ethdev/rte_ethdev.h                |  2 ++
>>   2 files changed, 21 insertions(+), 6 deletions(-)
>> 

      reply	other threads:[~2021-11-07 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 17:16 Martin Havlik
2021-10-27  9:55 ` Ferruh Yigit
2021-11-07 11:03   ` Havlík Martin [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=012de0bf4972b7c2f4534043038b451c@stud.fit.vutbr.cz \
    --to=xhavli56@stud.fit.vutbr.cz \
    --cc=ajit.khaparde@broadcom.com \
    --cc=aman.deep.singh@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=ferruh.yigit@intel.com \
    --cc=haiyue.wang@intel.com \
    --cc=humin29@huawei.com \
    --cc=ivan.ilchenko@oktetlabs.ru \
    --cc=kirankn@juniper.net \
    --cc=lirongqing@baidu.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viktorin@cesnet.cz \
    /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).