DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vivek Sharma <vivek.sharma@caviumnetworks.com>
To: dev@dpdk.org
Subject: [dpdk-dev] RTE-FLOW: PF vs PHY_PORT
Date: Wed, 22 Aug 2018 17:16:52 +0530	[thread overview]
Message-ID: <ae99760b-6920-9d3d-927d-d72747457b75@caviumnetworks.com> (raw)

Hi Devs,

I am trying to enable RTE-FLOW support on one of our platforms & having hard time in figuring out PF vs PHY_PORT differences and DPDK rationale for introducing these two distinct identities. 

Rte-Flow distinguishes between RTE_FLOW_ITEM_TYPE_PF & RTE_FLOW_ITEM_TYPE_PHY_PORT and

                                               RTE_FLOW_ACTION_TYPE_PF & RTE_FLOW_ACTION_TYPE_PHY_PORT.


I am finding it difficult to justify the presence of both these types, when functionality & implementation wise, these look quite similar. I would really appreciate if you could illustrate the differences between above item & action types by taking some hardware/platform as reference.


Thanks in advance,
Vivek Sharma

             reply	other threads:[~2018-08-22 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 11:46 Vivek Sharma [this message]
2018-08-27 13:11 ` Vivek Sharma
2018-08-27 13:45 ` Adrien Mazarguil

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=ae99760b-6920-9d3d-927d-d72747457b75@caviumnetworks.com \
    --to=vivek.sharma@caviumnetworks.com \
    --cc=dev@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).