DPDK usage discussions
 help / color / mirror / Atom feed
From: Juan Pablo L. <jpablolorenzetti@hotmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Event device library probs.
Date: Fri, 4 Nov 2022 17:40:48 +0000	[thread overview]
Message-ID: <AM0PR04MB66924860C90DC26EF78757D3D93B9@AM0PR04MB6692.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM0PR04MB66927AAB2E975005EAEBFCAFD9329@AM0PR04MB6692.eurprd04.prod.outlook.com>

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

Hello guys, no one has any suggestion please ? or  a check list what I should check to make sure it is working/configured please ? I have read the docs and I can't figure this out .. I'd appreciate any feedback at all ...

thank you!
________________________________
From: Juan Pablo L. <jpablolorenzetti@hotmail.com>
Sent: Friday, October 28, 2022 10:31 PM
To: users@dpdk.org <users@dpdk.org>
Subject: Event device library probs.

Hello everyone, I am trying to add support for the event device library to my application, but I have not been able to do it, i get the following problem at program start up:

w_probeeventdev vdev init() failed
vdev_probe(): failed to initialize event_sw0 device
EAL: Bus (vdev) probe failed.

I have tested the example application "eventdev_pipeline" with same results.

I m trying to create the device by passing the --vdev="event_sw0" flag to "rte_eal_init", I am trying with shared and static versions of dpdk (just in case idk) ... also tried with "rte_vdev_init" with same results.

I am also using in the same command line the following options (in case it matters):
--no-telemetry
--no-pci
--in-memory
--main-lcore 0
--lcores=(0)@(4), ....etc


I am surely missing something but can't pinpoint it, I would really appreciate any suggestions, thank you very much!

using dpdk-22.07



[-- Attachment #2: Type: text/html, Size: 7300 bytes --]

      reply	other threads:[~2022-11-04 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 22:31 Juan Pablo L.
2022-11-04 17:40 ` Juan Pablo L. [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=AM0PR04MB66924860C90DC26EF78757D3D93B9@AM0PR04MB6692.eurprd04.prod.outlook.com \
    --to=jpablolorenzetti@hotmail.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).