From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, roland@kernel.org,
jackm@dev.mellanox.co.il, amirv@mellanox.com,
matanb@mellanox.com
Subject: Re: [PATCH net-next 0/5] mlx4: Add support for single port VFs
Date: Thu, 20 Mar 2014 16:20:11 -0400 (EDT) [thread overview]
Message-ID: <20140320.162011.105658048451341992.davem@davemloft.net> (raw)
In-Reply-To: <1395245513-8139-1-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Wed, 19 Mar 2014 18:11:48 +0200
> The mlx4 Firmware && driver expose both ports of the device through one PCI function.
>
> This can be non-optimal under virtualization schemes where the admin
> would like the VF to expose one interface to the VM, etc.
>
> This series from Matan Barak adds support for single ported VFs.
>
> Since all the VF interaction with the firmware passes through the PF
> driver, we can emulate to the VF they have one port, and further create
> a set of the VFs which act on port1 of the device and another set which
> acts on port2.
>
> Series done against net-next commit 3ab428a "netfilter: Add missing
> vmalloc.h include to nft_hash.c"
>
> Roland, we send this through netdev, but if you have comments, will love
> to hear them.
Series applied, thanks.
prev parent reply other threads:[~2014-03-20 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:11 [PATCH net-next 0/5] mlx4: Add support for single port VFs Or Gerlitz
2014-03-19 16:11 ` [PATCH net-next 1/5] IB/mlx4_ib: Adapt code to use caps.num_ports instead of a constant Or Gerlitz
2014-03-19 16:11 ` [PATCH net-next 2/5] net/mlx4: Add data structures to support N-Ports per VF Or Gerlitz
2014-03-19 16:11 ` [PATCH net-next 3/5] net/mlx4: Add utils for N-Port VFs Or Gerlitz
2014-03-19 16:11 ` [PATCH net-next 4/5] net/mlx4: Adapt code for N-Port VF Or Gerlitz
2014-03-19 16:11 ` [PATCH net-next 5/5] net/mlx4: Adapt num_vfs/probed_vf params for single port VF Or Gerlitz
2014-03-20 20:20 ` David Miller [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=20140320.162011.105658048451341992.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.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).