From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Dexuan Cui <decui@microsoft.com>,
Yishai Hadas <yishaih@mellanox.com>,
Tariq Toukan <tariqt@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Mellanox ConnectX-3 VF driver can't work with 16 CPUs?
Date: Thu, 9 Feb 2017 18:47:33 +0200 [thread overview]
Message-ID: <032fd940-f0e8-4cd6-e455-8b8855c3105f@gmail.com> (raw)
In-Reply-To: <MWHPR03MB2669F7138EE9DE92A372C863BF450@MWHPR03MB2669.namprd03.prod.outlook.com>
Hi Dexuan,
On 09/02/2017 12:03 PM, Dexuan Cui wrote:
> Hi,
> While trying SR-IOV with a Linux guest running on Hyper-V, I found this issue:
> the VF driver can't work if the guest has 16 virtual CPUs (less vCPUs, e.g. 8, can work fine):
>
> [ 9.927820] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
> [ 9.927882] mlx4_core: Initializing b961:00:02.0
> [ 9.970994] mlx4_core b961:00:02.0: Detected virtual function - running in slave mode
> [ 9.976783] mlx4_core b961:00:02.0: Sending reset
> [ 9.985858] mlx4_core b961:00:02.0: Sending vhcr0
> [ 10.004855] mlx4_core b961:00:02.0: HCA minimum page size:512
> [ 10.010465] mlx4_core b961:00:02.0: Timestamping is not supported in slave mode
> [ 10.203065] mlx4_core b961:00:02.0: Failed to initialize event queue table, aborting
> [ 10.226728] mlx4_core: probe of b961:00:02.0 failed with error -12
>
> I'm using the mainline kernel (4.10.0-rc4).
>
> Any idea?
Thanks for your report.
We'll check this internally and get back to you.
Regards,
Tariq
>
> Thanks,
> -- Dexuan
>
next prev parent reply other threads:[~2017-02-09 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 10:03 Mellanox ConnectX-3 VF driver can't work with 16 CPUs? Dexuan Cui
2017-02-09 16:47 ` Tariq Toukan [this message]
2017-02-16 14:57 ` jackm
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=032fd940-f0e8-4cd6-e455-8b8855c3105f@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=decui@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.com \
--cc=yishaih@mellanox.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).