From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] doc: announce ABI change for struct rte_eth_conf
Date: Tue, 15 Dec 2015 03:00:19 +0000 [thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC22BF03B5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1610909.TYWkT8rdxQ@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, December 14, 2015 11:10 PM
> To: Liu, Jijiang
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3] doc: announce ABI change for struct
> rte_eth_conf
>
> > And tunneling packet encapsulation operation will benefit from the change.
>
> Sorry, I don't understand what you mean.
> Maybe others have a clue?
We want to add functions of tunneling packet decapsulation/encapsulation as APIs into DPDK, and it had better store tunnel configuration in a device's configuration, as a result, outer src/dst MAC address, outer src/dst IP address and others can be stored for a pair of queues.
The stored configuration can be used when encapsulating a tunneling packet for sending out via a specific queue.
And for RX side, we can use flow director or tunnel filter mechanism to guarantee a specific flow enter the a specific.
For example,
We do the following configuration,
rx_queue: 1
tx_queue: 1
Tunnel id: 1000
Outer Src MAC:
Outer dst MAC: 66.55.44.33.22.11
Outer Src IP:
Outer dst IP: 192.168.10.2
inner dst MAC: 22.33.44.55.66.77
And set RX classification condition for RX queue 1: Outer dst MAC + Tunnel id + inner dst MAC ( or 5 tuples), and decapsulate the tunneling packet and save some fields in the 'tunnel_conf' in the ' rte_eth_conf ',
then these stored configuration can be used when encapsulating a tunneling packet for sending out via TX queue 1.
> > The change of struct 'rte_eth_conf' like below, but it have not finalized yet.
> > struct rte_eth_conf {
> > ...
> >
> > struct rte_eth_tunnel_conf *tunnel_conf[RTE_MAX_QUEUES_PER_PORT];
> > /**< Tunnel configuration. */
> > };
> This rte_eth_conf struct is an input for rte_eth_dev_configure().
> Should we add some fields which are not used by rte_eth_dev_configure()
> but configured through rte_eth_dev_filter_ctrl() instead?
The tunnel configuration is not just for classification, we also need them to do encapsulation operation.
next prev parent reply other threads:[~2015-12-15 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 7:48 Jijiang Liu
2015-12-14 9:19 ` Chilikin, Andrey
2015-12-14 15:10 ` Thomas Monjalon
2015-12-15 3:00 ` Liu, Jijiang [this message]
2015-12-15 8:50 ` Ivan Boule
2015-12-18 2:00 ` Liu, Jijiang
2015-12-24 13:28 ` Ivan Boule
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=1ED644BD7E0A5F4091CF203DAFB8E4CC22BF03B5@SHSMSX101.ccr.corp.intel.com \
--to=jijiang.liu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).