From: Nidhia Varghese <nidhiavarghese93@gmail.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Adding multiple fields as key in ip_pipeline application
Date: Tue, 2 May 2017 14:58:48 +0530 [thread overview]
Message-ID: <CAAx9ALUqQAUgwatJmDKw4DRFua1M8ya4RprjPQJpUXR_D0OWXA@mail.gmail.com> (raw)
In-Reply-To: <54CBAA185211B4429112C315DA58FF6D31B5BCDF@IRSMSX103.ger.corp.intel.com>
Hi,
Can we do the append/prepend (of the port id with vlan id) through config
file?
Thanks,
Nidhia
On Fri, Apr 28, 2017 at 7:24 PM, Singh, Jasvinder <jasvinder.singh@intel.com
> wrote:
> Hi Nidhia,
>
>
> I am developing an application in which I need to use both incoming port
> and vlan as the key for the flow table. Port field is available at 24th
> byte of mbuf and vlan(single tagged) will be at 268th byte (128 mbuf + 128
> headroom + 12 ethernet header).
> How can I represent this in my config file in the src_mask field?
> Is there any way to take these fields separately and keep in headroom and
> then use them to calculate hash for lookup?
>
>
> [Jasvinder] - If you look at edge_router_upstream.cfg, pass-through
> pipeline have mask and offset defined for extracting the key from the
> packet header and storing in the headroom at the offset 128. This key is
> used in flow_classification pipeline to classify the flows. You can follow
> similar approach by using pass-through pipeline doing that action at the
> input port. For that, define mask (00000000FFFFFFFF) and offset fields for
> extracting the vlan-tag from the packet in pass-through pipeline and store
> at the desired offset in the headroom and prepend the vlan tag stored in
> the metadata with port id read from mbuf. In flow-classification pipeline,
> you can specify the headroom offset and mask to read the final key
> (portid+vlan tag) stored in the packet-metadata for classification.
>
>
>
> Thanks for your reply and help.
>
>
> Regards,
> Nidhia Varghese
>
--
Regards,
Nidhia Varghese
next prev parent reply other threads:[~2017-05-02 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 9:46 Nidhia Varghese
2017-04-28 13:54 ` Singh, Jasvinder
2017-05-02 9:28 ` Nidhia Varghese [this message]
2017-05-02 9:59 ` Singh, Jasvinder
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=CAAx9ALUqQAUgwatJmDKw4DRFua1M8ya4RprjPQJpUXR_D0OWXA@mail.gmail.com \
--to=nidhiavarghese93@gmail.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=users@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).