From: Ferruh Yigit <ferruh.yigit@intel.com>
To: xiangxia.m.yue@gmail.com, dev@dpdk.org
Cc: Tonghao Zhang <zhangtonghao@didichuxing.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/4] net/ixgbevf: unregister irq handler when other interrupts
Date: Mon, 30 Oct 2017 17:12:38 -0700 [thread overview]
Message-ID: <9e5c260f-20db-38f9-c92f-37aaed168b73@intel.com> (raw)
In-Reply-To: <1509026701-17478-1-git-send-email-xiangxia.m.yue@gmail.com>
On 10/26/2017 7:04 AM, xiangxia.m.yue@gmail.com wrote:
> From: Tonghao Zhang <zhangtonghao@didichuxing.com>
>
> When we bind the ixgbe VF (e.g 82599 card) to igb_uio and enable the
> rx-interrupt, there will be more than one epoll_wait on intr_handle.fd.
> One is in "eal-intr-thread" thread, and the others are in the thread
> which call the "rte_epoll_wait". The problem is that sometiems
> "eal-intr-thread" thread will process the rx interrupt, and rte_epoll_wait
> can’t get the event any more, and the packets may be lost.
>
> We should unregister the status interrupt handler in "eal-intr-thread"
> thread and the ixgbe is in the same case.
>
> Signed-off-by: Tonghao Zhang <zhangtonghao@didichuxing.com>
Thanks for the patches!
We are very close to 17.11 release and only fix patches are considered at this
phase, this patchset will be evaluated for next release.
Thanks,
ferruh
prev parent reply other threads:[~2017-10-31 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 14:04 xiangxia.m.yue
2017-10-26 14:04 ` [dpdk-dev] [PATCH v2 2/4] net/ixgbevf: set the inter-interrupt interval for EITR xiangxia.m.yue
2017-10-26 14:05 ` [dpdk-dev] [PATCH v2 3/4] net/ixgbevf: save IXGBE_VTEIMS to intr->mask for performance xiangxia.m.yue
2017-10-26 14:05 ` [dpdk-dev] [PATCH v2 4/4] net/ixgbevf: add check for rte_intr_enable xiangxia.m.yue
2017-10-31 0:12 ` Ferruh Yigit [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=9e5c260f-20db-38f9-c92f-37aaed168b73@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=xiangxia.m.yue@gmail.com \
--cc=zhangtonghao@didichuxing.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).