From: Yerden Zhumabekov <e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
To: Stephen Hemminger
<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] igb_uio: fall back to enable/disable irq mode
Date: Thu, 24 Jul 2014 09:11:36 +0600 [thread overview]
Message-ID: <53D07968.8030105@sts.kz> (raw)
In-Reply-To: <20140723110914.6b6902e8@haswell>
24.07.2014 0:09, Stephen Hemminger пишет:
>> Rewritten IRQ mode handling code introduced in commit 399a3f0d
>> (igb_uio: fix IRQ mode handling) renders some faulty NICs (VMware
>> e1000, for example) unusable if INTX mode is not supported.
>>
>> This patch gets these NICs up and running, but throwing a kernel
>> warning.
>>
>> Signed-off-by: Yerden Zhumabekov <e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
> That is because the VMWare PCI INTX is broken.
> The masking logic doesn't work.
>
> Rather than applying this patch a deeper fix in E1000 and DPDK handling
> of link state is needed. Better to just make the E1000 able
> to function without IRQ for Link state than just pretend masking works
I'll dig deeper then, maybe I'll figure out something.
If IRQ doesn't hook anything then, I guess, NIC should be continuously
checked for link state. If so, where should I put my efforts? PMD?
--
Sincerely,
Yerden Zhumabekov
STS, ACI
Astana, KZ
next prev parent reply other threads:[~2014-07-24 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 3:38 [PATCH] igb_uio dropped support for some faulty NICs Yerden Zhumabekov
[not found] ` <1406086726-54032-1-git-send-email-e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
2014-07-23 3:38 ` [PATCH] igb_uio: fall back to enable/disable irq mode Yerden Zhumabekov
[not found] ` <1406086726-54032-2-git-send-email-e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
2014-07-23 18:07 ` Stephen Hemminger
2014-07-23 18:09 ` Stephen Hemminger
2014-07-24 3:11 ` Yerden Zhumabekov [this message]
[not found] ` <53D07968.8030105-8EHiFRVJVgQ@public.gmane.org>
2014-07-24 15:11 ` 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=53D07968.8030105@sts.kz \
--to=e_zhumabekov-8ehifrvjvgq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.