From: Yong Liu <yong.liu@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 7/7] l3fwd-power: disable interrupt when wake up from sleep
Date: Thu, 29 Oct 2015 23:56:27 +0800 [thread overview]
Message-ID: <1446134187-4573-8-git-send-email-yong.liu@intel.com> (raw)
In-Reply-To: <1446134187-4573-1-git-send-email-yong.liu@intel.com>
Signed-off-by: Marvin Liu <yong.liu@intel.com>
diff --git a/examples/l3fwd-power/main.c b/examples/l3fwd-power/main.c
index 8bb88ce..9175989 100644
--- a/examples/l3fwd-power/main.c
+++ b/examples/l3fwd-power/main.c
@@ -798,6 +798,7 @@ sleep_until_rx_interrupt(int num)
port_id = ((uintptr_t)data) >> CHAR_BIT;
queue_id = ((uintptr_t)data) &
RTE_LEN2MASK(CHAR_BIT, uint8_t);
+ rte_eth_dev_rx_intr_disable(port_id, queue_id);
RTE_LOG(INFO, L3FWD_POWER,
"lcore %u is waked up from rx interrupt on"
" port %d queue %d\n",
--
1.9.3
next prev parent reply other threads:[~2015-10-29 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:56 [dpdk-dev] [PATCH v4 0/7] e1000: add rx interrupt support Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 1/7] e1000: enable device rx queue interrupt Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 2/7] e1000: separate lsc and rxq interrupt disable function Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 3/7] e1000: add ethdev rxq enable and " Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 4/7] e1000: add rxq interrupt handler Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 5/7] e1000: check lsc and rxq not enable in the same time Yong Liu
2015-10-29 15:56 ` [dpdk-dev] [PATCH v4 6/7] e1000: lsc interrupt setup function only enable itself Yong Liu
2015-10-29 15:56 ` Yong Liu [this message]
2015-10-29 18:18 ` [dpdk-dev] [PATCH v4 0/7] e1000: add rx interrupt support Thomas Monjalon
2015-10-30 1:32 ` Liu, Yong
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=1446134187-4573-8-git-send-email-yong.liu@intel.com \
--to=yong.liu@intel.com \
--cc=dev@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).