From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Getting mbuf pointer from buf_addr pointer
Date: Tue, 12 Jul 2022 14:22:09 +0300 [thread overview]
Message-ID: <20220712142209.4953c658@sovereign> (raw)
In-Reply-To: <CAO8pfFmMdsX2k2AsFH5sk+ukY=QLO3EpDy+Y2U2r_DKdeEVLqg@mail.gmail.com>
2022-07-12 12:30 (UTC+0200), Antonio Di Bacco:
> I was asked to reproduce the exact same behaviour of a library that
> used VMDQ queues without DPDK.
> Now this library offered an API to allocate a buffer for a packet and
> returned an address where the application could write its data.
>
> void* vmdqNew (vmdqUidPOOLt* p);
>
> I implemented the same API to allocate an MBUF from a pool and I also
> return the right address as a void* but then to transmit the packet I
> need the address of the MBUF for the tx_burst API and I don't have it.
Since you create mbufs and send them, the approach I mentioned is viable.
See rte_mbuf_buf_addr() and do the reverse to calculate the pointer to mbuf.
There is no API because it cannot work for any mbuf, but you case is limited
(there are chained mbufs, externally-attached mbufs, etc).
BTW, in general you could save a back-reference to the mbuf
just before the buffer you return from vmdqNew(), in pktmbuf private data.
But direct calculation is more efficient.
prev parent reply other threads:[~2022-07-12 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:21 Antonio Di Bacco
2022-07-12 8:32 ` Dmitry Kozlyuk
2022-07-12 10:30 ` Antonio Di Bacco
2022-07-12 11:22 ` Dmitry Kozlyuk [this message]
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=20220712142209.4953c658@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=a.dibacco.ks@gmail.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).