DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nidhia Varghese <nidhiavarghese93@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: [dpdk-dev] Getting meta data from different pipelines in ip_pipeline application
Date: Tue, 30 May 2017 12:33:49 +0530	[thread overview]
Message-ID: <CAAx9ALUJNc2=RVL36TuJg5wLWjrewXODPHVrfH2sPV0NY+__yQ@mail.gmail.com> (raw)

Hi,

This is how I want my pipelines to work:-
Pipeline 4:
Has to get the source mac address and save it in 160th(160-167) meta data
filed in the mbuf.
Pipeline 5:
Will take the vlan id and store it in 168th(168-175) offset of the same mbuf
Pipeline 6:
Take the incoming port id which is in 23rd position of the mbuf and store
it in 175th offset. (It will overlap with vlan id field stored, but since I
need only that one bit and I have to access all the three fileds together
as a 16 bit key value, I have done this overlapping)
Pipeline 7:
Key offset is given as 160 and key size is given as 16. So that 160 to 175
will be available as we have stored those in meta data in the previous
three pipelines.

I want to know whether my logic will work if I write the config file as
shown below. Will pipeline 7 be able to get the stored source mac address,
vlan id and port id from the given key offset?

[PIPELINE4]
..
..
dma_size = 8
dma_dst_offset = 160
dma_src_offset = 262
dma_src_mask = FFFFFFFFFFFF0000
dma_hash_offset = 192

[PIPELINE5]
..
..
dma_size = 8
dma_dst_offset = 168
dma_src_offset = 268
dma_src_mask = 00000FFF00000000
dma_hash_offset = 200

[PIPELINE6]
..
..
dma_size = 8
dma_dst_offset = 175
dma_src_offset = 23
dma_src_mask = FF00000000000000
dma_hash_offset = 208

[PIPELINE7]
..
..
key_size = 16
key_offset = 160
key_mask = FFFFFFFFFFFF000000000FFF000000FF
..

Thanks for your reply and help.

Regards,
Nidhia Varghese

             reply	other threads:[~2017-05-30  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  7:03 Nidhia Varghese [this message]
2017-06-01 12:58 ` Nidhia Varghese
2017-06-03 12:31   ` Dumitrescu, Cristian
2017-06-04  7:20     ` Nidhia Varghese
2017-06-07 17:08       ` Dumitrescu, Cristian

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='CAAx9ALUJNc2=RVL36TuJg5wLWjrewXODPHVrfH2sPV0NY+__yQ@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).