DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jack Humphries <jack@chillysky.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	users@dpdk.org, Haiyue Wang <haiyue.wang@intel.com>,
	david.hunt@intel.com
Subject: Re: Enable RX interrupts
Date: Sat, 06 Nov 2021 16:12:22 +0100	[thread overview]
Message-ID: <7085247.JFQ1STkTSE@thomas> (raw)
In-Reply-To: <8B6D83B4-DF17-4053-88D1-404CBCBB584F@chillysky.com>

01/11/2021 09:56, Jack Humphries:
> Hi Dmitry,
> 
> Thanks for the quick response! Yes, I was calling rte_eth_dev_rx_intr_enable — I just tried re-arming interrupts before each call to epoll and my initial experiment shows that fixes the issue.
> 
> You are right that l3fwd-power does the re-arming as well. If possible, it would be helpful to have a comment in that example code about the re-arming since the impression I got from quickly looking at the l3fwd-power code is that interrupts are turned off because the app wants to poll for a threshold of time before “giving up” and turning interrupts back on again. I’m happy to open a pull request to add this comment, too, if you prefer.

The best is to submit a patch on the mailing list, Cc'in the relevant maintainers.
Thanks




  reply	other threads:[~2021-11-06 15:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  5:50 Jack Humphries
2021-11-01  7:46 ` Dmitry Kozlyuk
2021-11-01  8:56   ` Jack Humphries
2021-11-06 15:12     ` Thomas Monjalon [this message]
2021-11-01 15:20 ` Stephen Hemminger
2021-11-01 19:16   ` Jack Humphries
2021-11-01 19:51     ` Stephen Hemminger

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=7085247.JFQ1STkTSE@thomas \
    --to=thomas@monjalon.net \
    --cc=david.hunt@intel.com \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=haiyue.wang@intel.com \
    --cc=jack@chillysky.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).