From: longtb5@viettel.com.vn
To: <vhuertas@gmail.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] Suggestions on how to customize the metadata fields of each packet
Date: Fri, 23 Feb 2018 10:13:45 +0700 (ICT) [thread overview]
Message-ID: <000f01d3ac54$dcd2cff0$96786fd0$@viettel.com.vn> (raw)
Hi,
First, I think your question should be sent to the user mailing list, not
the dev mailing list.
> 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.
If I'm not mistaken, the headroom is not where metadata provided by the NIC
are stored. Those metadata are stored in the rte_mbuf struct, which is also
128 bytes long.
The headroom area is located AFTER the end of rte_mbuf (at offset 128). By
default the headroom area is also 128 byte long, so the actual packet data
is stored at offset 256.
You can store whatever you want in this headroom area. However those
information are lost as soon as the packet leaves DPDK (the NIC will start
sending at offset 256).
-BL.
next reply other threads:[~2018-02-23 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 3:13 longtb5 [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-23 10:07 longtb5
2018-02-23 15:35 ` Victor Huertas
2018-02-23 8:12 Victor Huertas
2018-02-23 9:27 ` Ananyev, Konstantin
2018-02-22 17: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='000f01d3ac54$dcd2cff0$96786fd0$@viettel.com.vn' \
--to=longtb5@viettel.com.vn \
--cc=dev@dpdk.org \
--cc=vhuertas@gmail.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).