DPDK usage discussions
 help / color / mirror / Atom feed
From: Greg O'Rawe <greg.orawe@owmobility.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC - "PMD: net_mlx4: 0x55b8d8015b00: cannot attach flow rules (code 12, "Cannot allocate memory"), flow error type 2, cause 0x7f9ee4028200, message: flow rule rejected by device"
Date: Thu, 9 May 2019 13:02:40 +0000	[thread overview]
Message-ID: <VI1PR0701MB2142EEB59F7FEDCDCAC85165FB330@VI1PR0701MB2142.eurprd07.prod.outlook.com> (raw)

Hi,

I am experiencing a similar problem to the one you raised to the dpdk-users list in this thread:
https://mails.dpdk.org/archives/users/2018-October/003620.html

Were you ever able to resolve this issue to get DPDK working with the Mellanox Connect3-X card?

Many thanks

Greg O'Rawe



This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.

             reply	other threads:[~2019-05-09 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 13:02 Greg O'Rawe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-26 20:27 Junzhi Gong

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=VI1PR0701MB2142EEB59F7FEDCDCAC85165FB330@VI1PR0701MB2142.eurprd07.prod.outlook.com \
    --to=greg.orawe@owmobility.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).