DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Gilbert Carrillo <gcarrillo@ampex.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: DPDK 22.11 Troubleshooting
Date: Tue, 9 May 2023 10:42:57 +0100	[thread overview]
Message-ID: <ZFoVoTr9PTVMB3D4@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <SN7PR20MB61097B325B58CC661975393CB7719@SN7PR20MB6109.namprd20.prod.outlook.com>

On Mon, May 08, 2023 at 11:26:59PM +0000, Gilbert Carrillo wrote:
> 
> 
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com> 
> Sent: Wednesday, May 3, 2023 11:18 AM
> To: Gilbert Carrillo <gcarrillo@ampex.com>
> Cc: dev@dpdk.org
> Subject: Re: DPDK 22.11 Troubleshooting
> 
> On Wed, May 03, 2023 at 04:53:20PM +0000, Gilbert Carrillo wrote:
> > Make static returns an error (see attached).
> > 
> > v/R,
> > Gilbert
> >
> 
> To help investigate this issue, can you perhaps include the text of the full build output when you run "make static". On my system I see libelf listed on the linker flags when I run "make static", and things link properly. I'm wondering how my setup may differ from yours.
> 
> /Bruce
>  
> > -----Original Message-----
> > From: Bruce Richardson <bruce.richardson@intel.com>
> > Sent: Wednesday, May 3, 2023 10:35 AM
> > To: Gilbert Carrillo <gcarrillo@ampex.com>
> > Cc: dev@dpdk.org
> > Subject: Re: DPDK 22.11 Troubleshooting
> > 
> > On Wed, May 03, 2023 at 04:22:05PM +0000, Gilbert Carrillo wrote:
> > > Hi Bruce,
> > > 
> > > Thank you for the response.
> > > 
> > > There is no errors when I run the makefile, however I do see a difference in the programs. I don't believe the makefile is linking all the libraries together as intended.
> > > 
> > > For example, when I run the ethtool sample program and compile it using meson, it works fine and rte_eth_dev_count_avail() returns the correct amount. However, when I compile ethtool with the makefile and run it rte_eth_dev_count_avail() returns 0.
> > > 
> > 
> > Note that by default the meson build will statically link the examples, while the makefile will dynamically load the drivers at runtime. That may explain the difference. Can you try building and running using "make static" rather than just "make".
> > 
> > /Bruce
> 
> Bruce,
> 
> I had multiple versions of DPDK installed and I was linking the wrong one. I was able to compile my application with CMAKE successfully.
> 
> I had one last quick question. I am trying to achieve zero copy DMA from my FPGA to my external buffer. Is this possible? I saw methods such as attaching an mbuf to the external buffer? But I wasn't sure if this was truly zero copy.
> 
Attaching an mbuf to an external buffer would not involve any copy of the
data itself, so should be zero-copy. Each mbuf header contains a buffer
pointer, which normally points just to the end of the header structure, but
which can point to any other location in memory.

/Bruce

  reply	other threads:[~2023-05-09  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 22:27 Gilbert Carrillo
2023-05-03  8:28 ` Bruce Richardson
2023-05-03 16:22   ` Gilbert Carrillo
2023-05-03 16:34     ` Bruce Richardson
2023-05-03 16:53       ` Gilbert Carrillo
2023-05-03 17:13         ` Bruce Richardson
2023-05-03 17:18         ` Bruce Richardson
2023-05-03 17:25           ` Gilbert Carrillo
2023-05-08 23:26           ` Gilbert Carrillo
2023-05-09  9:42             ` Bruce Richardson [this message]
2023-05-09 14:16               ` Gilbert Carrillo
2023-05-09 14:52                 ` Bruce Richardson

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=ZFoVoTr9PTVMB3D4@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gcarrillo@ampex.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).