DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raunak Laddha <raunak.laddha@oracle.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Mike Banatt <mike.banatt@oracle.com>
Subject: [dpdk-dev] Problem while running dpdk
Date: Thu, 27 May 2021 22:05:39 +0000	[thread overview]
Message-ID: <BLAPR10MB5122D511FF280781A2612F558B239@BLAPR10MB5122.namprd10.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hello,
I am using dpdk 20.11.1 . I tried to use your resource to build a custom application which uses dpdk. I compiled my app using meson and makefile to see if I get different result for my issue. I have used pkg-config to load cflags and ldflags in my application and linking it as a static library.
Problem I am facing:
No buses are loaded. I can see that RTE_INIT_PRIO is used as constructor to load the buses. But in my application, buses are not loaded.
I tried to run the dpdk app named test-pipeline to check if it works and it does in that case. But same application with my makefile or meson file does not work.
First call in my program is rte_eal_init(argc, argv); (the init call of dpdk).
My app gets compiles. Also verified cflags and ldflags to check if dpdk flags are added.
My assumption is whatever RTE_INIT_PRIO is loading, it gets loaded correctly in dpdk test-pipeline app but not in my custom app.
Is there any config I am missing?
I have attached the makefile and meson file.

Thanks,
Raunak

[-- Attachment #2: test.c --]
[-- Type: text/plain, Size: 120 bytes --]

#include <stdio.h>
#include <rte_eal.h>

int main(int argc, char **argv) {
    rte_eal_init(argc, argv);
    return 0;
}

             reply	other threads:[~2021-06-01  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 22:05 Raunak Laddha [this message]
2021-06-01  8:03 ` Bruce Richardson
2021-06-01 14:40   ` [dpdk-dev] [External] : " Raunak Laddha

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=BLAPR10MB5122D511FF280781A2612F558B239@BLAPR10MB5122.namprd10.prod.outlook.com \
    --to=raunak.laddha@oracle.com \
    --cc=dev@dpdk.org \
    --cc=mike.banatt@oracle.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).