DPDK usage discussions
 help / color / mirror / Atom feed
From: 曾懷恩 <the@csie.io>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "Wenzhuo Lu" <wenzhuo.lu@intel.com>,
	"Konstantin Ananyev" <konstantin.ananyev@intel.com>,
	張敬昊 <frank@csie.io>,
	users@dpdk.org
Subject: Re: [dpdk-users] Flow director struct rte_flow_item_raw guild
Date: Thu, 16 May 2019 13:34:46 +0800	[thread overview]
Message-ID: <728B50C7-F3D8-4D9D-B569-66F29EB5D427@csie.io> (raw)
In-Reply-To: <20190513084911.GI4284@6wind.com>

Hi Adrien, 

Thanks for reply,

I tried to trace the mlx5 and ixgbe driver source code in DPDK source and notice that the flow director APIs are processed in it.

I also compared the difference of flow director APIs between both two drivers and found that there is no rte_flow_item_raw defined in mlx5 driver.

Is there any possible mlx5 series NICs support rte_flow_item_raw in the future?

Thanks a lot.

Best Regards,

> Adrien Mazarguil <adrien.mazarguil@6wind.com> 於 2019年5月13日 下午4:49 寫道：
> 
> On Sat, May 11, 2019 at 02:20:48AM +0800, Huai-En Tseng wrote:
>> Thanks for reply,
>> 
>> Actually I’d like to use  rte_flow_item_raw structure with PPP header, the ICMP format is my little trial.
> 
> OK, makes sense, there's no pattern item for PPP yet.
> 
>> I will try X520 next week.
>> 
>> Another question, is ixgbevf also support RTE_FLOW_ITEM_RAW?
> 
> The ixgbe driver looks like it does but I'm not sure regarding the VF
> variant, Cc'ing maintainers just in case.
> 
> -- 
> Adrien Mazarguil
> 6WIND


  reply	other threads:[~2019-05-16  5:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  2:01 曾懷恩
2019-05-09  2:10 ` 張敬昊
2019-05-09  3:51   ` 曾懷恩
2019-05-09 12:38     ` Adrien Mazarguil
2019-05-10  6:38       ` 曾懷恩
2019-05-10 13:44         ` Adrien Mazarguil
2019-05-10 18:20           ` Huai-En Tseng
2019-05-13  8:49             ` Adrien Mazarguil
2019-05-16  5:34               ` 曾懷恩 [this message]
2019-05-16  6:00                 ` Tom Barbette
2019-05-22  3:18                   ` 曾懷恩

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=728B50C7-F3D8-4D9D-B569-66F29EB5D427@csie.io \
    --to=the@csie.io \
    --cc=adrien.mazarguil@6wind.com \
    --cc=frank@csie.io \
    --cc=konstantin.ananyev@intel.com \
    --cc=users@dpdk.org \
    --cc=wenzhuo.lu@intel.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).