DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: "orika@nvidia.com" <orika@nvidia.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "humin29@huawei.com" <humin29@huawei.com>
Subject: [dpdk-dev] How about public rte flow lock API
Date: Tue, 6 Apr 2021 17:32:02 +0800	[thread overview]
Message-ID: <c86703bd-b8d6-61b3-dda3-0a67c3cd3f2a@huawei.com> (raw)

Hi, Ori and Ferruh

    Currently, the rte flow API has the lock of flow_ops_mutx default which
used when driver hasn't provided mutex protection, it's inner API which was
not public, but in hns3 driver there maybe concurrent access driver's rte flow
data when doing reset recovery (which occur in intr thread) and upper-layer
application calling flow API.

    We think it's best to use framework's lock mechanism (i.e. flow_ops_mutex),
but currently it can't address hns3's requirement (as described above).

    There maybe three schemes:
    A) public the rte flow lock API.
    B) driver direct access the framework's flow_ops_mutex.
    C) driver adds one new mutex and delcare RTE_ETH_DEV_FLOW_OPS_THREAD_SAFE.

    we prefer use the scheme A, how about your opinion ?


Best regards


                 reply	other threads:[~2021-04-06  9:32 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=c86703bd-b8d6-61b3-dda3-0a67c3cd3f2a@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=humin29@huawei.com \
    --cc=orika@nvidia.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).