From: Nidhia Varghese <nidhiavarghese93@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Subject: [dpdk-users] Adding multiple fields as key in ip_pipeline application
Date: Fri, 28 Apr 2017 15:16:16 +0530 [thread overview]
Message-ID: <CAAx9ALUPhQjrdy87Ak8uT2o+KRu3hzUdBmHXMYW9=c4XN9s5ng@mail.gmail.com> (raw)
Hi,
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?
Thanks for your reply and help.
Regards,
Nidhia Varghese
next reply other threads:[~2017-04-28 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 9:46 Nidhia Varghese [this message]
2017-04-28 13:54 ` Singh, Jasvinder
2017-05-02 9:28 ` Nidhia Varghese
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='CAAx9ALUPhQjrdy87Ak8uT2o+KRu3hzUdBmHXMYW9=c4XN9s5ng@mail.gmail.com' \
--to=nidhiavarghese93@gmail.com \
--cc=dev@dpdk.org \
--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).