From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
wenzhuo.lu@intel.com, helin.zhang@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fix interrupt block issue
Date: Mon, 16 Jan 2017 13:42:09 +0000 [thread overview]
Message-ID: <a5373cdf-1fe3-f17c-8b23-f492d5e5be72@intel.com> (raw)
In-Reply-To: <1484528629-18298-1-git-send-email-qi.z.zhang@intel.com>
Hi Qi,
On 1/16/2017 1:03 AM, Qi Zhang wrote:
> When handle link status change interrupt, interrupt
> will be blocked until delayed handler finish, the
> duration is at least 1 second, this may cause following
> VF to PF mailbox traffic be blocked and sometimes PF
> can't ack to VF in time before VF think it's time out.
> This patch remove this limitation, interrupt will be
> enabled before interrupt handler finish, and a flag is
> used to prevent re-entering delayed handler.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
Can you please rebase patch to latest next-net?
Some part of this patch conflicts with the work that removes direct
access from eth_dev to pci_dev.
Thanks,
ferruh
prev parent reply other threads:[~2017-01-16 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 1:03 Qi Zhang
2017-01-16 13:42 ` 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=a5373cdf-1fe3-f17c-8b23-f492d5e5be72@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@intel.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).