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 11:32:34 +0300 [thread overview]
Message-ID: <20220712113234.1209dd36@sovereign> (raw)
In-Reply-To: <CAO8pfFneeFnGZNxPeXTAMwe4cxXoACvWX7XhS-wGsG0RrNcgYA@mail.gmail.com>
2022-07-11 11:21 (UTC+0200), Antonio Di Bacco:
> Is there any API that allows me to get the MBUF pointer given its
> buf_addr pointer?
No.
How did you come across this need?
Sounds like an app design flaw.
What is the original problem you're solving?
P.S. It may be possible in specific cases when you know (from code)
how mempool sets buf_addr for a given mbuf,
and that PMDs don't change buf_addr with the used set of offloads.
Apparently, this approach would be extremely brittle and dangerous.
next prev parent reply other threads:[~2022-07-12 8:32 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 [this message]
2022-07-12 10:30 ` Antonio Di Bacco
2022-07-12 11:22 ` Dmitry Kozlyuk
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=20220712113234.1209dd36@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).