DPDK usage discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Ye Xiaolong <xiaolong.ye@intel.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Why flow can not be created?
Date: Fri, 02 Aug 2019 15:06:19 +0900	[thread overview]
Message-ID: <20190802150619.D107.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <20190731113045.8EC1.17218CA3@ntt-tx.co.jp_1>

Helllo Experts,

Q1. Are there any NICs which supports entag/detag VLAN?
I searched source DPDK source code with keyword "OF_POP_VLAN" or "OF_POP_VLAN"
and found some codes within mlx5_flow_tcf.c and cxgbe_flow.c.

Q2. Are there any plans in DPDK community to update document about 
NIC to update support of rte_flow?
I have heard the situation about document form Adrien, and to be honest
I felt it is very hard to take try and error with testpmd for every NIC.

BR<
Hideyuki Yamashita
NTT TechnoCross


  reply	other threads:[~2019-08-02  6:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  6:08 Hideyuki Yamashita
2019-07-22 12:48 ` Ye Xiaolong
2019-07-23  6:26   ` Hideyuki Yamashita
2019-07-30 10:37     ` Hideyuki Yamashita
2019-07-30 12:25       ` Adrien Mazarguil
2019-07-31  2:30         ` Hideyuki Yamashita
2019-08-02  6:06           ` Hideyuki Yamashita [this message]
2019-08-06  9:12             ` Adrien Mazarguil
2019-08-06  9:59               ` Moti Haimovsky
2019-08-09  6:05               ` Hideyuki Yamashita
2019-08-14  5:56                 ` [dpdk-users] How L2 broadcast is handled under rte_flow? Hideyuki Yamashita
2019-08-29  3:11                   ` Hideyuki Yamashita

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=20190802150619.D107.17218CA3@ntt-tx.co.jp_1 \
    --to=yamashita.hideyuki@ntt-tx.co.jp \
    --cc=adrien.mazarguil@6wind.com \
    --cc=users@dpdk.org \
    --cc=xiaolong.ye@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).