From: Victor Huertas <vhuertas@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Suggestions on how to customize the metadata fields of each packet
Date: Thu, 22 Feb 2018 18:35:01 +0100 [thread overview]
Message-ID: <CAGxG5ciiEGvYd-TK3i+zWXwhbhrUz_a6ydvRwmezLaUA0K0u2A@mail.gmail.com> (raw)
Hi all,
In the project I am working I need to define custom metadata fields on each
packet once they are captured using DPDK.
I have seen that each packet has a headroom memory space (128 bytes long)
where RSS hashing and other metadata provided by the NIC is stored. This
information will be useful for me but I need to add some further fields to
these metadata without having to modify the source code of the library.
Do you which is the best practice to do it? Do I have for example to define
a struct that contains rte_mbuf struct and additional metadata struct?
struct new_packet{
struct rte_mbuf;
struct additional_metadata
}
I would appreciate it if you could provide me with some guidelines to know
how to implement it.
Thanks a lot
--
Victor
next reply other threads:[~2018-02-22 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 17:35 Victor Huertas [this message]
2018-02-23 3:13 longtb5
2018-02-23 8:12 Victor Huertas
2018-02-23 9:27 ` Ananyev, Konstantin
2018-02-23 10:07 longtb5
2018-02-23 15:35 ` Victor Huertas
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=CAGxG5ciiEGvYd-TK3i+zWXwhbhrUz_a6ydvRwmezLaUA0K0u2A@mail.gmail.com \
--to=vhuertas@gmail.com \
--cc=dev@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).